On 2015-12-09 22:22 , Alexander Holand Salgado wrote:
Thanks for confirming my suspicion. Yes, nested withTransaction would not provide the results you might first think you'd get and should probably not be allowed. But, I'm still thinking that its worth looking at supporting nesting withTransaction within a cacheConnection as this should be fine - but that might be something for the dev mailinglist.(?)
Alternately, Grails manages connections and nested transactions (using Spring), but that's on a higher level than groovy.sql.Sql.
Cheers, 11011011
