Databases
StackOverflow2013
Postsdbo
POIssue with inheritance and constraints in Grails/GORM
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIssue with inheritance and constraints in Grails/GORM
    primarykey
    data
    text
    <p>Not sure how to frame this question, but I am seeing some behavior that I am unable to explain ... any help will be highly appreciated. I have a super-class <code>Form</code>, and sub-class <code>DraftForm</code>. The super-class has a more stringent constraint on a property <code>content(blank: false)</code> than the sub-class <code>content(nullable: true)</code>, and I am using <code>tablePerHierarchy false</code>. The domain classes are as follows.</p> <pre> class Form { String content static constraints = { content(blank: false) } static mapping = { tablePerHierarchy false } } </pre> <pre> class DraftForm extends Form { static constraints = { content(nullable: true) } } </pre> <p>With the above domain models, the following test * passes * without any problem.</p> <pre> class DraftFormIntegrationSpec extends Specification { void "Testing a draft-form and a form derived from a draft-form"(){ given: "A draft-form with invalid form-fields" // 1 def draftForm = new DraftForm() when: "The draft-form is validated" // 2 assert draftForm.validate() == true then: "The draft-form has no error" // 3 !draftForm.hasErrors() when: "The draft-form is saved" // 4 try{ draftForm.save() }catch(Exception e){ println "Exception thrown!" println e.class } then: "The draft-form is not found in the database" // 5 draftForm.id == null when: "The draft-form is casted to a form" // 6 Form form = (Form) draftForm assert form.validate() == true then: "The form validates, and has no error" // 7 !form.hasErrors() } } </pre> <p>Here are my questions: <li>I think a sub-class also inherits the super-class's constraints. In that case, how come the draft form validates fine and has no error even though the <code>content</code> is <code>null</code> (please see // 2 and // 3 in the test)? <li>If the draft-form validates fine, why do I get an exception (// 4) and cannot find the draft-form in the database (// 5)? <li>When the <code>DraftForm</code> is type casted to a <code>Form</code>, it still validates fine and has no error (// 6 and // 7), even though the <code>content</code> property is still <code>null</code>. How is that possible?</p> <p>Thank you for the help!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStikka
    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. POIssue with inheritance and constraints in Grails/GORM
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`save()` return the instance or null so in your tests you need to use `assert draftForm.save() != null` or `draftForm.save(failOnError:true)`.
      singulars
      1. POIssue with inheritance and constraints in Grails/GORM
      1. USSérgio Michels
    2. COThanks @Sergio. If I did `draftForm.save(failOnError: true)` without the try-catch, the test does fail by throwing an exception when it tries to save. However, I am puzzled that the `draftForm` validates without any issue (// 2) and has no error (// 3), but still I cannot save it. Although, the fact that I cannot save explains `draftForm.id == null` (// 5), but still I cannot explain how it can validate without any error but still cannot save.
      singulars
      1. POIssue with inheritance and constraints in Grails/GORM
      1. UStikka
 

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