On Fri, Oct 4, 2013 at 2:55 PM, Sascha Sertel <sascha.ser...@gmail.com>wrote:
> > I'm working on a multi-platform app that uses a cross-platform library with > SQLite 3.7.16.1 built into it (i.e. not using the built-in SQLite version > in Android or other platforms). We make (re)use of prepared statements for > INSERT and UPDATE on the database, and we use FULLMUTEX serialized > threading mode. We use explicit transactions for some bulk INSERT > operations, but most other calls use implicit transactions. > > Everything worked fine until I switched journal_mode from MEMORY to WAL. > Now when I run the app I started seeing SQLite errors pop up, the first > error is > > > sqlite3_step failed: unable to open database file (error code: 14) > Please activate the error and warning log (http://www.sqlite.org/errlog.html) and let us know what you see there. One possible problem: SQLite needs to create a temporary file so that a multi-row update can be backed out if a constraint fails, but you are out of temporary file space, or maybe you don't have access rights on the temporary file space. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
