Currently the symantics of Hibernate are such that changes to the db are automatically performed and committed if an loaded Object is modified. So the User Object changes to the Database are performed when groovy execute "u.properties = params". So the Object is modified, but u.save() was never called.
Seems that the loaded Object is bound to the Hibernate Session, so Hibernate checks the Object for changes.
I think this is very critical, because the Grails validation won't work correct.
So a validation Error is displayed, but the Object has been modified ?!
Is there a method to evict the Object from the Hibernate Session? (u.evict() doesn't work).