-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/12/12 10:35, dd wrote: > i mean, for every write operation in a table.
You should specify some of your other constraints and exactly what it is you are trying to achieve (*not* how you are trying to achieve it). The solutions range from implementing undo by using triggers to save old values, through using a virtual table that backs up data somewhere else. The SQLite backup API only works on the whole database. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlDE5poACgkQmOOfHg372QQI8gCeP6GfezJUWQ7M3pdfvvgc2FCp J1QAoMSM/tbpxlicrrDpTbgjHAsWln1d =mPMA -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users