A Framework for
Time Travel
in a relational database
A Framework for
Time Travel
in a relational database
What does 'Navigate the Now' mean?
Well, as inserts, updates and deletes occur in your data they naturally create different versions of the truth. In a database that inherently understands Time the developer easily accesses any version by simply saying when 'Now' is, knowing that the only data projected back will be that which is valid at that time.
Navigating the Now is the ability to move to any moment in Time and have all related data available for that moment in Time.
Developers can build functionality at a fraction of the cost when the database understands Time.
Applications can navigate through a perfect audit of relational data in the context of Time.
Artificial Intelligence can access sophisticated Time-Series across Entity Life Histories.
Data integrity is maintained at Entity Life History level i.e. past, present and future versions using declarative constraints. No overlaps, No gaps, No temporal mistakes.
Developers are only going to adopt new approaches if it makes their coding lives easier and more productive.
The key is to 100% insulate developers from direct manipulation of time-stamped data be that at row level or table level.
Developers work with relational because over the years it has continued to be one of the best options for enterprise requirements. The heart of relational is working in the Current View. This is exactly where developers need to be when designing schemas and writing code.