Re: [sqlite] 'database disk image is malformed' only on the mac

I can now reliably corrupt my database - and this happens only when some other process is writing to the database while I perform sqlite3_close_v2 on the connections. I'll explain what I'm doing. Since the last I wrote, I've disabled all the flags other than these: #define SQLITE_ENABLE_FTS3 1

Re: [sqlite] 'database disk image is malformed' only on the mac

oncurrency though. The app has various plugins that can at any time access and write to the same database that's already in-use by the main app. Will this pose a problem with DELETE or TRUNCATE journaling? Thanks Fahad -- Sent from: http://sqlite.1065341.n5.

Re: [sqlite] 'database disk image is malformed' only on the mac

Thanks Jens, yes I didn't take the warnings from the Thread Sanitizer lightly. Although I'm very confident with the actual implementation (using thread local dictionaries) and have verified time and again using unit tests that my code is otherwise thread-safe, I really do think there are perhaps

Re: [sqlite] 'database disk image is malformed' only on the mac

No I'm not. -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] 'database disk image is malformed' only on the mac

I've tried that as well. Since I'm using PRAGMA journal_mode=WAL on all the connections, I've had issues with MMAP (as acknowledged by the threads above) so have had to disable that. I also need FTS 3 to work. The rest of the flags to do with synchronisation and threading, I've enabled / disabled

Re: [sqlite] 'database disk image is malformed' only on the mac

I apologise for the many posts, but I'm writing in hope that one of you may point out something that I'm either doing wrong, or a concept I haven't fully grasped. I'm aware that prepared statements are tied to the database connection they were created for. In order to get more speed out of my

Re: [sqlite] 'database disk image is malformed' only on the mac

I can't be certain now but I think this thread is related: http://sqlite.1065341.n5.nabble.com/Re-Database-corruption-and-PRAGMA-fullfsync-on-macOS-td95366.html It was this thread that I landed on earlier this year to presumably fix the issues I was experiencing personally. This did help, in

Re: [sqlite] 'database disk image is malformed' only on the mac

any of the benefits of multi-threading? Would that help? I should add that I switched to WAL earlier this year and ever since have had issues reported, at least once a week. Nowadays it's almost once a day. With journal_mode DELETE I never had an issue, but then the app was pretty serial then. Tha

Re: [sqlite] 'database disk image is malformed' only on the mac

, I'm unable to reliably corrupt the db but I could sit and repeat the steps 20 times and have it go corrupt at least once before. Now I've been trying for over two hours and it seems to be okay. regards Fahad -- Sent from: http://sqlite.1065341.n5.nabble.com

Re: [sqlite] 'database disk image is malformed' only on the mac

Hi Simon I tried it with sqlite3_shutdown(), didn't help. I was able to reproduce it again using the main app and the safari share plugin. Main App: Finished writing to db, just opened a new connection to read (after opening a connection I set PRAGMA query_only=1; PRAGMA read_uncommitted=1; and

[sqlite] 'database disk image is malformed' only on the mac

test SQL amalgamation (v3.20.0) with the following compile time options: #define SQLITE_ENABLE_FTS3 1 #define SQLITE_THREADSAFE 2 #define SQLITE_DEFAULT_MEMSTATUS 0 #define SQLITE_ENABLE_STAT4 1 #define SQLITE_MAX_MMAP_SIZE 0 #define SQLITE_OMIT_DEPRECATED 1 #define SQLITE_OMIT_SHARED_CACHE 1 Any help would