Re: [sqlite] After upgrade from sqlite3 3.8.7.4 to anything after 3.14.1, I get "Error: destination database is in use"

2018-08-21 Thread Richard Hipp
O it looks to me like the > 'exclusive' command just needs to be removed ... the threadsafe option that > sqlite3 was built with looks like it is internally handling the locking. That would be my guess too. -- D. Richard Hipp d...@sqlite.org ___ sqlite

Re: [sqlite] After upgrade from sqlite3 3.8.7.4 to anything after 3.14.1, I get "Error: destination database is in use"

2018-08-21 Thread Brian Hutchinson
Is this question better suited for the development list? No response at all. Thanks, Brian ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] After upgrade from sqlite3 3.8.7.4 to anything after 3.14.1, I get "Error: destination database is in use"

2018-08-10 Thread Brian Hutchinson
Running sqlite3 in an embedded Linux distributed environment. Sqlite3 was built with Yocto and configured to be threadsafe. One box keeps a master database and periodically will rsync the database to remote boxes and send them a message to "update" their database. When "update" message is receiv