Hi there,

Your use case for time travel on views is really interesting. I can see why being able to track historical versions of both views and their underlying tables would be crucial for an application that relies on caching and granular queries. Right now, as you mentioned, this feature isn’t natively supported in most systems, but it’s definitely an area where many analytics platforms are evolving.

On a slightly different note, I was recently exploring nz-tourism datasets for a project, and I found that having proper time-travel support could be a game-changer for analyzing trends over time—like visitor numbers or seasonal patterns—without worrying about the underlying changes in data sources. It really shows how valuable this feature could be, not just for enterprise applications but also for analytics on evolving datasets.

Hopefully, the platform roadmap includes this enhancement soon, as it would make historical analysis and reproducibility much more seamless.

Cheers!