On 8 May 2018, at 1:12pm, Simon Slavin <slav...@bigfraud.org> wrote: > You can lock the database yourself, using BEGIN EXCLUSIVE or BEGIN IMMEDIATE > depending on which you want. Then do all the backup stuff, then COMMIT or > ROLLBACK without having changed anything.
On 9 May 2018, at 1:50am, Donald Shepherd <donald.sheph...@gmail.com> wrote: > Having just tested that (for alternate purposes), it doesn't work. The > sqlite3_backup_step calls following a "BEGIN IMMEDIATE" instruction > returned SQLITE_LOCKED. Oops. I assume you did the lock using the same connetion that was calling the backup API. In which case I apologise for the incorrect information. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
