On Tue, May 6, 2014 at 2:59 PM, Clemens Ladisch <clem...@ladisch.de> wrote: > With the COMMIT, you told the database that the transaction succeeded > (which means that the effects of all successful statements are saved > permanently.) If you want the transaction to fail, execute ROLLBACK > instead.
But that's only possible for interactive SQL sessions. You cannot "branch" in SQL "scripts" (successions of SQL commands) one executes via sqlite3[.exe] at the command line. Using the ROLLBACK conflict resolution on the insert is the only way to achieve what he wants as described, short of switching to a "programmatic" environment to run his "scripts" for full branching, etc... --DD _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
