On 17 Apr 2012, at 12:33am, Petite Abeille <[email protected]> wrote:
> On Apr 17, 2012, at 12:51 AM, Simon Slavin wrote: > >> Now, consider what it takes if you're logging value changes instead of >> commands issued. Your first problem is figuring out which rows exist. > > Why? Each row is time boxed. There is no ambiguities about what exists when. You're starting from the point where you know which row you're looking for. I'm not sure how you knew the 'where foo.foo_key = 1' part of your SELECT. So in your reconstruction scenario, which question are you answering ? Are you 1) trying to reconstruct the entire database 2) trying to reconstruct all the data about a particular entity: find the row for a customer named "ACME INC." 3) trying to find a number of rows: find all customers who a particular salesman was managing Your procedure is the right solution for 4) I know the rowid of the record I'm interested in But I don't know if that's the scenario Puneet was interested in, or if that's something which would happen in real life: needing to reconstruct that row, and not caring about any of the other data in the database. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
