Quoth BareFeetWare <list....@barefeetware.com>, on 2010-12-23 15:10:30 +1100: > Is there a way to do this in pure SQL, without my application code > having to check for errors along the way and then interrogate the > SQL to look for a "commit" type line and replace it? This seems > pretty error prone and convoluted.
Why would you introspect the SQL rather than generating the beginning and end of the transaction from a different part of the application code to each statement inside? Begin transaction, then start executing statements from a list; if any of them fail, stop executing further statements and roll back, otherwise commit at the end. Don't include the begin/end in the list. Does that not work for you? > Thanks, > Tom > BareFeetWare ---> Drake Wilson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
