8 ms·
You can do it all yourself if you want, but Datomic does it for you without you having to do anything. Also as it does it on a datom level it is a lot more eff
by pelle 14y ago
You can do it all yourself if you want, but Datomic does it for you without you having to do anything.
Also as it does it on a datom level it is a lot more efficient than versioned rows.
Interestingly one of the early selling points of Postgresql was this time travel functionality. But it was yanked out in 6.2
http://www.postgresql.org/docs/6.3/interactive/c0503.htm http://www.postgresql.org/docs/6.3/interactive/c0503.htm
- mbreese 14y agoYes, but you also loose the flexibility of not doing it. I'd rather work in an established RDMBS and configure in the design I'd like to use rather than use a database that requires a specific configuration. I'm sure that Datomic has it's place, but the examples you gave in this post aren't that convincing.
- pelle 14y agoI agree with you this is not on its own necessarily a good reason to switch to Datomic. I will be getting into more detailed examples later. My real point with this post was more to talk about how to model the data using datoms and not specifically the temporal aspects of it. I made many mistakes in my original data models in datomic based on many years of rdbms thinking.