Earlier quoted context omitted.
Okay, so it's a database with version control. I was actually looking for a feature like this a while back in normal databases.
In the database world, we call it temporal databases, because it introduces the concept of time as a first-class part of the conceptual/logical model. Every production database I've ever seen goes through some version of the same evolutionary lifecycle: 1. "We only need the current state". The database acts as a snapshot of the current world. Updates cause the loss of historical data. The database is like a state mac…
Any database that uses a append only log can potentially be temporal so long as it retains the log and exposes the information in the log (which most don't).
Even say PostgreSQL uses a form short term temporal querying in order to provide MVCC, to bad they haven't taken it further to allow fully temporal standards.