Developing Time-Oriented Database Applications in SQL (2000) [pdf](cs.arizona.edu)
cs.arizona.edu
Developing Time-Oriented Database Applications in SQL (2000) [pdf]
http://www.cs.arizona.edu/people/rts/tdbbook.pdf
6 comments
As I understand it that is one of the selling points of the product Datomic. The database in its entirety effectively can be worked with as a value type.
Please check out datomic!
http://www.datomic.com/
http://www.datomic.com/
Oracle flashback (https://en.m.wikipedia.org/wiki/Oracle_Flashback) pretty much does this.
I believe you mean Oracle Total Recall (http://www.orafaq.com/wiki/Oracle_Total_Recall).
Along with the references others have given, SQL Server 2014+ has temporal tables which do exactly what you are describing.
Even if you keep full query logs, getting to the state the database was 10th of February 2014 05:34:23 UTC is rather inconvenient and slow.
You wouldn't need bitemporal schemas either with a feature like this.
Another pet peeve in relational databases is a no-compromise hierarchy (and graph) storage. You can usually get fast reads or fast inserts, but there always seems to be a compromise.