On Apr 16, 2012, at 11:01 PM, Kit wrote: >> - how do you represent deleted rows? > > I will create a new record with attribute "deleted" and new timestamp.
So there is now a new attribute that indicates deletion? Which needs to be included in all queries? In addition to the time aspect? Why a different way to indicate deletion from time boxing? > >> - how do you avoid version ambiguities (e.g. two rows created with the same >> timestamp)? > > UNIQUE index on (t.doc_id,t.created_on) So one cannot make more than one change per second? What happen if multiple changes occur at the same time granularity? > ---------------- > A modified select: > SELECT doc.record, t.rec, t.created_on FROM doc LEFT JOIN t ON doc.id=t.doc_id > WHERE doc.id=id_xx AND created_on<time_xx > GROUP BY t.doc_id > HAVING created_on=max(created_on); The above will return deleted rows, no? Shouldn't it include that new "deleted" attribute? Also... why an outer join? Why two tables? Is it mostly for auditing? Not versioning? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
