On 3 Apr 2013, at 10:52pm, Nico Williams <n...@cryptonector.com> wrote:
> As a user I prefer continuous saving + infinite undo. Undo is difficult with SQLite. For instance, to undo an UPDATE command you need to know the original values of all the fields updated, which may be different in different rows. One way to do it is to continue to write different files, possibly using the backup API as mentioned upthread. Another way is to keep a log of the SQLite commands issued. To undo you simply start from a saved state and 'replay' all the commands up to the undo point. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
