On 12 Nov 2012, at 7:15pm, Stephen Chrzanowski <pontia...@gmail.com> wrote:
> I *KNOW* doing transactional work (Even just standard selects) can cause > problems via a network share with SQLite due to networking `bugs` or > whatever. My question is, does/would the backup api have the same problem > if I were to backup a remote file to memory or local storage, work on data > locally, then when needed, write back to the original location with the > same backup mechanism? The backup system would work. But making any change to a database while the backup API is being used causes its backup to restart (that's how it works !). In other words, for the backup API to complete, no changes must be made to the file it's backing up for a long time -- proportional to the length of the file. If this happens naturally during the use of your database (you get odd times when nothing happens for a few minutes) then your system will work. On the other hand, if the database is under constant use (during a working day or on a multi-user web-facing system) then your backup will never complete until the load goes away. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
