I'm the author of SQL Fiddle. That knowledge may help frame this question:
I am attempting to write some Groovy code which will execute any arbitrary query/DML code in my database. Based on my reading of the Groovy Sql API, all of these functions expect something very particular. For example, "eachRow" expects there to be a resultset returned; if it isn't returned (as in the case of an UPDATE statement, for example) then using it will throw an error. I am able to call "execute" with any type of statement, however I can't get back a resultset for my SELECT statements when using that (which is definitely a requirement).
At this point I'm thinking I might have to abandon Groovy's Sql library in favor of some lower-level JDBC implementation. This would be a shame, I think, but I'm willing to go there if necessary. I would greatly prefer to keep this as Groovy-esqe as possible, though. How might I go about doing that?