- From: Aaron Boodman <aa@google.com>
- Date: Wed, 17 Oct 2007 14:32:38 -0700
On 10/17/07, Scott Hess <shess at google.com> wrote: > A) As things currently stand, the developer simply can't roll their > own transaction structure. Passing BEGIN, COMMIT, or ROLLBACK to > executeSql() doesn't do anything sensible. It's possible you could > somehow do something using temporary tables, but that's going to be > really dependent on your underlying SQL implementation's capabilities. Yes this is an icky bit. I am almost ready to say that BEGIN/COMMIT/ROLLBACK should be blacklisted, except for the fact that I can see somebody wanting to programatically rollback in the space between two sql statements and the only way without ROLLBACK is to throw an error. - a
Received on Wednesday, 17 October 2007 14:32:38 UTC