System.Data.SQLite

 A multi-threaded app that ran perfectly well with 1.0.60.0 frequently but randomly gives the "Unable to open the database file" error with 1.0.61.0.

When I removed "journal mode=persist" from the connection options the problem went away.

I suspect that this is really a change in the behaviour of the bundled SQLite library and that it has nothing to do with System.Data.SQLite itself.

Danny

---

 

 

 

This is known bug in SQLite 3.6.12+ and it's resolved in SQLite 3.6.14 (to be released in 3 days). There's currently no way to work around it and setting journal_mode to persist only masks the problem, so it doesn't happen that often. See http://www.sqlite.org/cvstrac/tktview?tn=3821 for details.

 As 3.6.14 (And subsequently 3.6.15) have been release; Are we likely to see a new release of System.Data.SQLite using a newer version of SQLite?

 I'm using 1.0.61.0 in Windows Mobile and I'm seeing this issue as well. My connection string has the "Synchronous=Full;" option enabled and all of my database access acquires a lock before performing any (Read only operations included) database access.All connections have journal_mode = memory, locking_mode = exclusive and temp_store = memory pragma operations set before being returned to the calling code.

When this exception is thrown all other threads are either in non-database sections of code or waiting to acquire the lock before performing database access, so I'm fairly confident that the mentioned SQLite race condition is the culprit. I'm happy to help nail this issue by sending stack traces / trying to provide a reproducible snippet of code.

I will have the 62 release finished early next week, matched up of course to the newest SQLite engine.

 

Excellent news!

I'd be happy to test a pre-release and let you know if it fixes my issue / help debug it.