On 16 Apr 2012, at 7:29pm, Puneet Kishor <punk.k...@gmail.com> wrote:
> So, if a query returns one or more rows today, the same query (that is, the > same query params with an additional time stamp param) should return exactly > the same result 3 years from now even if the rows themselves may have been > modified. If your system can accept UPDATE commands which multiple rows, then the only way to do it correctly is to use a TRIGGER. SQLite triggers automatically execute once per row changed. All alternatives involve writing your own parser for SQL commands. However, one way to achieve your requirements efficiently is extremely simple: just log all UPDATE and INSERT commands. Save them, plus a timestamp, in a file, either a text file or a SQLite database. When you need to reconstruct your database at any date/time, simply replay your transcript up to that data/time. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
