On 5 Sep 2015, at 9:18pm, Petr L?z?ovsk? <lazna at volny.cz> wrote: > Have some shell scripts working with sqlite. Receiving incoming payments from > bank via HTTP API and pushing it into database. This script will start > periodically, every single hour. > > Want to prevent situation only few payments are written and script failed for > some reason. Have read about sqlite transactions and understood so I should > start every writing sequence with BEGIN; statement, than made all inserts and > than COMMIT; statement. Is this all how it is working? Should I do something > more to prevent such unwanted situation?
You have it correct. If you put multiple change commands in one transaction, then either they are all executed or none of them are executed. Even if your program crashes in the middle of a command, when SQLite opens the file again it works out what happened and restores a 'clean' database. Theoretically you would have to always open a transaction for SQL. Issuing INSERT before BEGIN would result in an error message. But SQL is kind and opens a one-command transaction if you forget. Simon.
