-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/12/12 21:44, dd wrote: > Sometimes, sqlite databse corrupts.
That is the problem you need to fix. If you have a system that is unreliable then it will also corrupt your backups. http://www.sqlite.org/lockingv3.html#how_to_corrupt http://www.sqlite.org/howtocorrupt.html > So, I want to take online backup of specific table. Not entire > database. Do you need to take a backup on every change, as part of the change or is it acceptable to make backups periodically and possibly lose intermediate versions of the data? For a periodic backup you can iterate over the table contents and output them in a convenient format for you, such as CSV or SQL statements. For saving all data you can use triggers to save historical values in a second table and then do a periodic backup. If it must be immediate then the only choice available is to use a virtual table and do the backup during writes/sync. This is all considerably more work than figuring out why you are getting corruption in the first place. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlDGF2IACgkQmOOfHg372QTo9gCfSQQwreSvsa9lrV/wj0YC2Fvj LT0AmwdZSaNvVJJuic3gLYmQfn9YX6x3 =Gx1r -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
