On 2014/02/12 10:09, Stephen Chrzanowski wrote:
The other thing I'd look into is that because of the varying speeds of SD, the volume of information you could be writing, you may run into an issue where you call the backup API but due to write speeds, something else writes to the live in-memory database, and then your data becomes expunged when the DELETE command is executed while the backup is happening.
Actually, the Backup-API is clever like that, it will automatically void and re-start the backup when data changes happen. Of course this might be equally detrimental if you update more frequently than the backup takes to complete, in which case the system would be in permanent backup and any gains voided.
Maybe stop the updater till the backup is finished... it should however not take 10s, so it _should_ be safe, but I would put it in the precautionary wait state just to be safe.
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
