I prefer to COMMIT TRANSACTION, because 1. As a rule, all successfully executed transactions should be commit, otherwise should be rollback. 2. To rollback a transaction with no errors occurred will misguide some developers. 3. if someone puts a writing statement or function in the " read only" transaction incidentally, there will be a difference, "ROLLBACK TRANSACTION" always return a misguided SQLITE_OK, but "COMMIT" will inform you SQLITE_SNAPSHOT_BUSY or SQLITE_LOCK or something else additionally.
My 2 cents. ________________________________ ???: Olivier Mascia<mailto:om at integral.be> ????: ?2016/?1/?14 23:54 ???: SQLite mailing list<mailto:sqlite-users at mailinglists.sqlite.org> ??: [sqlite] Best way to terminate a dead-transaction: commit or rollback? Hello, Let a transaction (started with BEGIN TRANSACTION) which did only reads. Is it any better to end it by COMMIT TRANSACTION or ROLLBACK TRANSACTION, or is it completely insignificant? -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
