On Thursday, September 19, 2013 12:50:27 PM UTC-7, Nobu Games wrote: > > I just did some digging around and your error code translates into the > following define constant: > *SQLITE_IOERR_FSTAT*<http://sqlite.org/c3ref/c_abort_rollback.html> > > So basically it's an fstat error which according to this > thread<http://sqlite.1065341.n5.nabble.com/reasons-for-SQLITE-IOERR-FSTAT-td66646.html>can > happen when you try to access the database after it (or one of the > journal files) have been deleted. > Others<http://t3391.codeinpro.us/q/51502007e8432c04261a3ca8>also mention that > this error has to do with changing data while another > thread is trying to read it simultaneously. I guess the "write-ahead" > journaling of SQLite does not mix well with thread concurrency. In my > experience you should try to synchronize all concurrent read and write > access to your SQLite database yourself and not rely on the built-in > locking facilities (they never worked for me correctly). >
Your eyes are sharp, I couldn't decode that one. I do think I will have to tighten up the concurrency, without knowing beforehand if it will help. At the time this occurs, nothing *should* be writing, but I already know of one bug that may make that untrue. Multiple threads could be reading. I think they just block but who knows. I am not using write ahead, which the docs tell me should be off by default. Nathan -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
