Why should a failure in transaction #2 rollback transaction #1? If you want this behaviour, do "begin; delete ...; insert ... on conflict rollback; commit;" to make both statements run in one transaction
-----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Cecil Westerhof Gesendet: Montag, 09. Juli 2018 08:21 An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Betreff: [EXTERNAL] [sqlite] What happens when a call contains two SQL statement I am working with Tcl. The best is of-course a general answer, but if it is depending on the used language I will be satisfied with the Tcl answer. ;-) Say I have the following code: set SQLCmd " DELETE FROM testing WHERE key = 12 ; INSERT INTO testing (key, value) VALUES (12, 'Just some text') " db eval ${sqlCmd} If the insert goes wrong, will the delete be rolled back, or not? I could use INSERT OR REPLACE, but the above code would be database independent. -- Cecil Westerhof _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick | Software Engineer | Scientific Games International GmbH | Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien, DVR: 0430013 | (O) +43 1 80100 - 0 May be privileged. May be confidential. Please delete if not the addressee. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
