On Aug 19, 2010, at 4:00 PM, David Bicking wrote: > I haven't tried RAISE(ROLLBACK... as that seems to severe. > RAISE(ABORT... removes the initial insert to Table1, which I want to avoid. > RAISE(FAIL.. on lets say the fourth record inserted in to Table2, would leave > the first three there, which I can't let happen. It is all or nothing for > data changes below Table1. > > Which leads me to believe I can't do what I want without application code > supervising the changes.
Would SAVEPOINTs help you here? http://www.sqlite.org/lang_savepoint.html I've never tried using ROLLBACK TO in a trigger. e _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
