Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well first of all lets correct it, you can use <code>inheritance</code> in this case. You just need to change the convention of <code>has a</code> relationship to <code>is a</code> relationship.</p> <p>Few factors to keep note of: 1. Grails works on convention over configuration. 2. You can use GORM which wraps the persistence layer and creates an Object Mapping for the underlying persistence layer with the help of Hibernate.</p> <p>As per your functional requirement:-</p> <p>If you do not want to have the <code>User</code> as part of persistence you can have an <code>abstract</code> class <code>User</code> which can hold the common properties of the User including the <code>openId</code> attribute. It has to be placed in <code>src\groovy</code> directory as per convention (since the base class is abstract, dependency injection will be defied)</p> <p>The same goes for <code>Property</code>. Abstract <code>Property</code> class in <code>src\groovy</code>.</p> <p>Now coming to the business models, <code>extend</code> each of the concrete entities (<code>domain</code> classes) from the <code>abstract</code> parent.</p> <p>Summary:-</p> <ul> <li><p>Create grails app</p></li> <li><p>Under src\groovy(for example, I am considering a basic structure):</p></li> </ul> <p>User.groovy:-</p> <pre><code>abstract class User{ String name String emailId OpenID openId } </code></pre> <p>Property.groovy:-</p> <pre><code>abstract class Property{ String propertyName } </code></pre> <ul> <li>Under <code>grails-app/domain</code>:</li> </ul> <p>Librariran.groovy:-</p> <pre><code>class Librarian extends User{ //Attributes specific to Librariran static constraints = { } static mapping = { } } </code></pre> <p>Book.groovy:-</p> <pre><code>class Book extends Property{ //Attributes specific to Book static constraints = { } static mapping = { } } </code></pre> <p>So on and so forth. Groovy objects under grails-app/domain are considered concrete entities by Grails convention. More information you can obviously find <a href="http://grails.org/doc/latest/guide/GORM.html">here</a>. You can also use composition if you come across scenarios, in fact I already mentioned that in <code>User</code> having <code>OpenId</code>.</p> <p>Note:- This is context to latest version of Grails (> 2.x)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to design domain classes in Grails?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdmahapatro
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to design domain classes in Grails?
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks! But as I understand it, if I put the abstract classes in src/groovy, there will be no User and Property tables created in the database. Am I correct? I'm assuming our client would want a table for all Users and for all Properties.
      singulars
      1. PO
      1. USrenz
    2. COYes, in that case you can have both of them as domain objects inside grails-app/domain.
      singulars
      1. PO
      1. USdmahapatro
 

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