
In GORM 6.0.x the default was to use Hibernate’s dirty checking mechanism Which will output null for the description with GORM 6.1.4, switching back to GORM 6.0.11 in gradle.properties makes it output the description as expected. zip once started with grails run you can test by opening: Grails Version (if using Grails): 3.2.10.
#Gorm save method map of parameters mac os x#
Operating System: Mac OS X 10.12 Sierra. That causes the Dirt圜heckable.$changedProperties to be assigned an empty map and GrailsEntityDirtinessStrategy.isDirty returns false as the direct field sets for the fields don't mark them as dirty. It seems related to dirtyness checking, with the activateDirt圜hecking call added to GrailsEntityDirtinessStrategy.onPostLoad in commit a007266 Since GORM 6.1 this no longer saves the value of the fields. Updating a field directly using a method on A should persist that change to the database Actual Behaviour Create a controller with methods to create A & B entities, set the individual fields on A using the created methods and list A objects.
Create two methods on A, one to update description, one to update b.A should have a toString method which prints details of the fields A should have two fields: String description, B bĢ.2. Full description of the issue provided (see below)Ģ.1.Example that reproduces the problem uploaded to Github.