Grails

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.4, 1.1
• Fix Version/s: 1.1.1
• Component/s: Persistence
• Labels:

  None

If you retrieve a persistent domain instance and set one or more invalid properties in a controller and attempt to save the instance in a transactional service method, validation isn't performed and the instance is flushed. If one of the validation problems involves a database constraint (e.g. nullable) then the call fails due to a database constraint violation.

I've attached a sample project to illustrate. Create a Thing instance and then edit it. Set the name to NULL, which forces the value to null since empty form fields are blank, not null. Rather than validating the instance and logging the messages, you'll get an error page with the error

org.springframework.dao.DataIntegrityViolationException:
not-null property references a null or transient value: Thing.name

I spent some time debugging this a while back and it looks like the call to the services getMetaClass() ends the transaction and triggers a flush, so the call to thingService.saveThing() never actually executes - you can see that from the console log messages.

I saw this in a 1.0.4 app and it's a problem in 1.1, but I haven't tested in 1.0.5.

1. 

   bug.tar.gz

   11/Apr/09 11:47 AM

   126 kB

   Burt Beckwith

• Assignee:

  Graeme Rocher

  Reporter:

  Burt Beckwith

• Created:

  11/Apr/09 11:47 AM

  Updated:

  27/Jul/09 5:12 AM

  Resolved:

  22/Apr/09 7:54 AM