Re: [sqlite] [EXTERNAL] What happens when a call contains two SQL statement

Only the "on conflict" clause -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Cecil Westerhof Gesendet: Montag, 09. Juli 2018 08:38 An: SQLite mailing list Betreff: Re: [sqlite] [EXTERNAL] What happens when a cal

Re: [sqlite] [EXTERNAL] What happens when a call contains two SQL statement

2018-07-09 8:28 GMT+02:00 Hick Gunter : > Why should a failure in transaction #2 rollback transaction #1? > ​I was thinking that, but was not sure. I thought that maybe everything in a call would be seen as a transaction. But that is not the case then: every statement in a call is its own transac

Re: [sqlite] [EXTERNAL] What happens when a call contains two SQL statement

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...@mailinglist