On Wed, Dec 3, 2014 at 10:18 AM, Simon Slavin <slav...@bigfraud.org> wrote:
> > On 3 Dec 2014, at 3:10pm, Hick Gunter <h...@scigames.at> wrote: > > > SQLITE_BUSY means that some connection is BUSY with a write transaction > and has locked the database file; presumably, it will be possible to write > to the database when the current writer has finished, just not now or > within the specified busy timeout. > > > > SQLITE_LOCKED otoh means that the calling application is in error and > has specified two or more transactions whose table access modes are > incompatible and whose table access orders differ. This situation is > resolvable only if at least one involved transaction is rolled back. > > This is very illuminating and far better information than I managed to > find in the official SQLite documentation. It would be really helpful if > something like this could be incorporated in an appropriate place. > > https://www.sqlite.org/rescode.html#busy -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
