In one of the modules that I was working on , I needed to delete the previous data from a table then load up the data into those tables again and then manipulate code through the ‘id’s’ on those tables.
\nSo this is what I was doing …<\/p>\n
[groovy] This made realise that truncate was a better option … But unfortunately<\/strong> the GORM layer does not support the ‘ truncate ‘ queries that I was looking for. So with some help from ‘ Mr. Google ‘ and my fellow colleagues , i realised that there was another way to do this .. [groovy] def session = sessionFactory.getCurrentSession() The getCurrentSession()<\/strong> method looks at the current context to see if a session is stored in there. If there is one, it uses it, and if there isn’t a session in the current context, it creates a new one and saves it in there. Hope this helps .. \ud83d\ude00<\/p>\n Cheers<\/p>\n Manoj Mohan In one of the modules that I was working on , I needed to delete the previous data from a table then load up the data into those tables again and then manipulate code through the ‘id’s’ on those tables. So this is what I was doing … [groovy] Event.executeUpdate(‘delete from Event’) EventInstance.executeUpdate(‘delete from EventInstance’) […]<\/p>\n","protected":false},"author":32,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":4,"footnotes":""},"categories":[7],"tags":[4843,844,4840,843],"class_list":["post-3611","post","type-post","status-publish","format-standard","hentry","category-grails","tag-database","tag-executeupdate","tag-grails","tag-truncate"],"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
\nEvent.executeUpdate(‘delete from Event’)
\nEventInstance.executeUpdate(‘delete from EventInstance’)
\n[\/groovy]
\n<\/br>
\nBut the problem<\/strong> was that when I deleted the events, the ‘id’s’ on those tables would remain intact and the new Events that would load up would continue upon the earlier present ‘ id’s ‘ .i.e if the last present id was 24 before deleting , the new load-ups would continue from 25 onwards..<\/p>\n
\nSo in effect this query would give an error
\n<\/br>
\n[groovy]
\nEvent.executeUpdate(‘truncate table Event’)
\nEventInstance.executeUpdate(‘truncate table EventInstance’)
\n[\/groovy]<\/p>\n
\n Session Factory …<\/strong>
\nSession Factory allowed me to truncate those tables through\u00a0 createSQLQuery() method
\nSo my new approach was
\n<\/br><\/p>\n
\n def sessionFactory<\/p>\n
\n Query query = session.createSQLQuery(‘truncate table event’)
\n[\/groovy]<\/p>\n
\nThen all I did was use the query to truncate the tables… and presto !! .. my work was done ..
\n<\/br><\/p>\n
\nManoj (at) Intelligrape (dot) com<\/p>\n","protected":false},"excerpt":{"rendered":"