Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://www.linkedin.com/in/rjgeyer" rel="nofollow noreferrer">Ryan Geyer</a> has a very interesting article <a href="http://blog.ryangeyer.com/2010/03/09/modularizing-your-grails-application-domain-classes/" rel="nofollow noreferrer">Modularizing your Grails application domain classes</a> which lists 3 solutions to this problem:</p> <ol> <li>As a <strong>RESTful JSON Service</strong> - easy to get this setup in Grails but then you lose the automatic GORM functionality.</li> <li><strong>Separate out the domain classes into a library JAR file</strong> and reference that library in both of my other applications. This is not as easy as it first sounds</li> <li><p><strong>Create a Grails plugin.</strong> Put the domain object in the plugin. Each of your applications can then import this plugin. You can then create different controllers with different functionality as required. The sample code for this is available at:</p> <p><code>git clone git://ec2.nslms.com/grails/blog_example_modular</code></p></li> </ol> <p>Ted Naleid gives a great tip later in the <a href="http://blog.ryangeyer.com/2010/03/09/modularizing-your-grails-application-domain-classes/#comment-250108075" rel="nofollow noreferrer">post</a> and recommends...</p> <blockquote> <p>"create a grails-app/conf/BuildConfig.groovy file and put the plugin name and path to the source in it. ... If you do this, <strong>your applications will see the live changes to your domain/controller/service/etc classes as if they were actually in current app</strong> and there isn't any need to repackage and reinstall the plugin when you make changes."</p> </blockquote> <p><a href="http://www.nslms.com/2010/03/10/modularizing-your-grails-application-domain-classes/#comment-442091111" rel="nofollow noreferrer">Using memcache</a> should enable both applications to have a consistent view of the data and would avoid each individual application having it's own inconsistent cache. </p>
    singulars
    1. This table or related slice is empty.
    1. POHow to implement a "remote" Domain?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdexterous
    1. USChris
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to implement a "remote" Domain?
      singulars
      1. PTQuestion
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGreat answer, but solutions 2 and 3 still need both apps connected to the database :-( I need a solution more like your solution 1. I am aware that I will loose some functionality, but I guess I can solve this through caching (use a locak domain as cache domain and only remote requests to .get(id))
      singulars
      1. PO
      1. USrdmueller
    2. COIf you're going with option 1, json-rest-api is a great plugin for setting up!
      singulars
      1. PO
      1. USgotomanners
    3. COjson-rest-api looks great! At least, that's a solution for one side of my problem :-)
      singulars
      1. PO
      1. USrdmueller
 

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