From your description it really sounds like a system based on a functional programming language. Lists of immutable objects operated on by functions that accept a "time t" parameter and lazy evaluation.
I love the idea of a database that can be queried "as of time t". I seem to remember that PostgreSQL used to support that as a neat trick of MVCC (version 4 or 5?) but on larger tables with heavy use the transaction IDs rolled over too quickly.
Posted May 9, 2012 18:04 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)
[Link]
Yes, it has the same ideas as functional programming. But such kind of logic must be implemented on the application level, it's not appropriate at the database level.