[sqlite] Possible bug with locking/retying

Discussion of SQLite Database Betreff: [sqlite] Possible bug with locking/retying In searching for something else I came across this: <http://beets.radbox.org/blog/sqlite-nightmare.html> I don't like the fact that it's undated. For all I know this is about a three year old bug which has

[sqlite] Possible bug with locking/retying

On Sun, 3 May 2015 01:18:11 +0100 Simon Slavin wrote: > In searching for something else I came across this: > > > > I don't like the fact that it's undated. For all I know this is > about a three year old bug which has long since been

[sqlite] Possible bug with locking/retying

> I think it's a misuse of Sqlite and not a real bug. He adds code to ensure > only one thread access the database in a multithread application. For the > description, I infer he uses -DSQLITE_THREADSAFE=2 (multithread), where a > -DSQLITE_THREADSAFE=1 (serialized) solve the problem better

[sqlite] Possible bug with locking/retying

In searching for something else I came across this: I don't like the fact that it's undated. For all I know this is about a three year old bug which has long since been patched. I understand the description, but not what SQLite does

[sqlite] Possible bug with locking/retying

If you look here: http://beets.radbox.org/blog/, you can see the blog entry is dated August 24th, 2012. Peter On 5/2/2015 5:18 PM, Simon Slavin wrote: > In searching for something else I came across this: > > > > I don't like the fact that