Am 07.03.2012 13:21, schrieb Marcus Grimm: > > On 07.03.2012 13:13, Eduardo Morras wrote: >> At 12:22 07/03/2012, you wrote: >>> Dear list, >>> >>> I'm using the backup api to frequently backup >>> a running sqlite database. >>> >>> I'm wondering if the backup API is able to detect a corrupt >>> database or will it simply also backup a corrupt DB ? >>> >>> I evaluating the need to issue a (timeconsuming) "pragma >>> integrity_check" prior >>> running the backup to avoid that a backup will be overwritten >>> with an invalid database. >> >> You can do the backup and after that do an integrity check on the >> backup. Surely you're backing up on a different >> server, don't you? If the back up pass the integrity check it a real >> backup, if not, launch a warning. > > Yeah, that's a good idea. > Ohh boy, why I didn't think about that my self ? :-)
In this process, you have to prevent that you overwrite your last "working" backup! Which database will you use, if you realize, that the backup is a corrupt database? On a webserver you should have enough space to make additional copies. In an embedded environment, this could be difficult. Thomas > > Thanks > > Marcus > >> >>> Sure I could try to simulate that, but probably somebody here >>> knows the answer. >>> >>> Thank you. >>> >>> Marcus >> >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
