On Mon, 12 Aug 2019 12:02:33 +0200 Kira Backes <kira.bac...@nrwsoft.de> wrote:
> I would change the error description for SQLITE_BUSY_SNAPSHOT so that > it no longer says "read transaction" but instead says "read > transaction or ongoing select statement". While I agree the documentation could be clarified, that wouldn't be a particularly good change. A "read transaction" is, exactly, an "ongoing select statement". More precisely, the *execution* of a SELECT statement is a read transaction, whether or not preceded by BEGIN TRANSACTION. The person reading the documentation is expected to know that. It's defined by SQL, and has nothing to do with the SQLite implementation. I think you actually got burned by multithreading. Let's just say you're not the first. ;-) To the extent the documentation could be made clearer, I would suggest it focus on the interface and not the implementation. Knowledge of locks, while interesting, should not be required to use transactions correctly or to understand SQLITE_BUSY_SNAPSHOT. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
