{"id":1557,"date":"2010-09-07T16:54:58","date_gmt":"2010-09-07T11:24:58","guid":{"rendered":"https:\/\/tothenewco.pro\/blog\/?p=1557"},"modified":"2016-12-19T15:06:07","modified_gmt":"2016-12-19T09:36:07","slug":"gorm-goodies-read-discard-refresh","status":"publish","type":"post","link":"https:\/\/tothenewco.pro\/blog\/gorm-goodies-read-discard-refresh\/","title":{"rendered":"GORM goodies read, discard, refresh"},"content":{"rendered":"

Grails docs are the best source to understand how to make best use of GORM methods and now the GORM Gotcha’s series By Peter Ledbrook<\/a> is also making the docs easy to understand.
\nSo many time it happens when the domain instance values gets updated without calling save method.It happens because the object is attached to hibernate session, to change this behavior we can use the method like read instead of get\/load.
\nWhat read actually do is <\/p>\n

\r\nPerson person = Person.read(1)\r\nprintln \"Output -: ${person?.firstname}\"  \/\/ Output -: Uday\r\nperson.firstname=\"Uday1\"\r\nprintln \"Output -: ${person?.firstname}\" \/\/ Output -: Uday1\r\n<\/pre>\n
The value is changed but it is not stored in the database. But the changes can be saved into the database if you explicitly call save().  <\/p>\n
The other approach could be removing the object from hibernate session, so that the changes made to the database do not get persisted to the database <\/p>\n
\r\nPerson person = Person.get(1)\r\nprintln \"Output -: ${person?.firstname}\"  \/\/ Output -: Uday\r\nperson.firstname = \"Uday1\"\r\nprintln \"Output -: ${person?.firstname}\" \/\/ Output -: Uday1\r\nperson.discard()\r\nprintln \"Output -: ${person?.firstname}\"  \/\/ Output -: Uday1\r\n<\/pre>\n
In above example, any change made to the object do not get persisted to the database . Again it will save the changes if you explicitly call save(). <\/p>\n
One more good method is refresh() which is used to load the object again from the database, so all the changes made to object will be reverted. Though it is not advisable but sometimes if you want to get the object to its original stage you can do it by refresh. <\/p>\n
\r\nPerson person = Person.get(1)\r\nprintln \"Output -: ${person?.firstname}\" \/\/ Output -: Uday\r\nperson.firstname = \"Uday1\"\r\nprintln \"Output -: ${person?.firstname}\" \/\/ Output -: Uday1\r\nperson.refresh()\r\nprintln \"Output -: ${person?.firstname}\" \/\/ Output -: Uday\r\n<\/pre>\n
These are the few goodies which are available with the GORM and we can use according to our use case :).
\n<\/p>\n
Hope it helps
\nUday Pratap Singh<\/a>
\nuday@intelligrape.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Grails docs are the best source to understand how to make best use of GORM methods and now the GORM Gotcha’s series By Peter Ledbrook is also making the docs easy to understand. So many time it happens when the domain instance values gets updated without calling save method.It happens because the object is attached […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":18,"footnotes":""},"categories":[7],"tags":[383,385,384,386],"class_list":["post-1557","post","type-post","status-publish","format-standard","hentry","category-grails","tag-automatic-update-in-grails","tag-discard-usage","tag-read-usage","tag-refresh-usage"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t