Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think converters (<code>as JSON</code> syntax) will only work on domain objects and collections by default.</p> <p>To convert arbitrary objects you should use the <code>encodeAsJSON()</code> converter, I believe. Or use an object marshaller, where you tell the converter how to deal with your object.</p> <p>The docs aren't very clear on this though..</p> <p>See:</p> <ul> <li><a href="http://grails.org/Converters+Reference" rel="noreferrer">http://grails.org/Converters+Reference</a> (object marshalling section at bottom)</li> <li><a href="http://grails.org/doc/latest/ref/Plug-ins/codecs.html" rel="noreferrer">http://grails.org/doc/latest/ref/Plug-ins/codecs.html</a></li> </ul> <p>But I note that <a href="http://grails.org/doc/latest/api/grails/converters/JSON.html#JSON%28java.lang.Object%29" rel="noreferrer">http://grails.org/doc/latest/api/grails/converters/JSON.html#JSON%28java.lang.Object%29</a> says that the object converts POGOs.. Maybe it means if you have a marshaller?</p> <p>I did find this reference too:</p> <blockquote> <p>Notice that the ‘as’ operator is not overloaded for plain objects ...</p> <p>Domain objects can use the ‘as’ operator to cast an object to JSON, the same as a collection. So unlike POGOs, where they must be massaged into a list or have encodeAsJSON explictly called ...</p> <p><a href="http://manbuildswebsite.com/2010/02/08/rendering-json-in-grails-part-2-plain-old-groovy-objects-and-domain-objects/" rel="noreferrer">http://manbuildswebsite.com/2010/02/08/rendering-json-in-grails-part-2-plain-old-groovy-objects-and-domain-objects/</a></p> </blockquote> <p>Which seems to describe the situation.</p>
    singulars
    1. This table or related slice is empty.
    1. POUnable to use "as JSON" after upgrading to grails 2.1.1 from grails 1.3.4
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsync
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the reply! This is a domain object and it worked on v 1.3.4.
      singulars
      1. PO
      1. USmdamman
    2. COOk, I wouldn't be that surprised if it stopped working from the 1 > 2 upgrade, but since it's a domain object that is puzzling!
      singulars
      1. PO
      1. USsync
    3. COrelated: http://jira.grails.org/browse/GRAILS-6222 "Default JSON ObjectMarshallers should be configured when Grails ApplicationContext does not exist"
      singulars
      1. PO
      1. USMykennaC
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload