Re:Developing Time-Oriented Database Applications in SQL (20...
by frou_dh on Thursday October 01, 2015 @03:01PM
(#10313737)
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.
Re:Developing Time-Oriented Database Applications in SQL (20...
by rymndhng on Thursday October 01, 2015 @02:59PM
(#10313720)
Please check out datomic!
Re:Developing Time-Oriented Database Applications in SQL (20...
by sgolestane on Thursday October 01, 2015 @04:16PM
(#10314330)
Oracle flashback (https://en.m.wikipedia.org/wiki/Oracle_Flashback) pretty much does this.
Re:Developing Time-Oriented Database Applications in SQL (20...
by needusername on Friday October 02, 2015 @01:33AM
(#10316888)
I believe you mean Oracle Total Recall (http://www.orafaq.com/wiki/Oracle_Total_Recall).
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.