For clarification- am I correct that what you are referring to as "time travel" is simply a history list of prior queries you've run? Can I today, run a query and see what the results would have been in the database last month (or yesterday, or 2 hours ago, etc)?
I also understood that, but seems unreasonable to be able to achieve it without somehow storing the state via scd or some sort of audit + multi engine support
Sure it's a complex, difficult feature. But that's what "time travel" typically means in terms of querying databases. It's the headline of this article, the fact that what they really mean is a simple query log, is kind of bait-and-switch.
Comments
For clarification- am I correct that what you are referring to as "time travel" is simply a history list of prior queries you've run? Can I today, run a query and see what the results would have been in the database last month (or yesterday, or 2 hours ago, etc)?
I also understood that, but seems unreasonable to be able to achieve it without somehow storing the state via scd or some sort of audit + multi engine support
Sure it's a complex, difficult feature. But that's what "time travel" typically means in terms of querying databases. It's the headline of this article, the fact that what they really mean is a simple query log, is kind of bait-and-switch.