3 ms·
What's an actual use-case for this? I am reading the documentation but still don't see why I should use it and what the actual advantages compared to current so
by nik736 10y ago
What's an actual use-case for this? I am reading the documentation but still don't see why I should use it and what the actual advantages compared to current solutions are.
- yrashk 10y agoIt was built as a kind of a database constructor for event sourced / journalled systems. It's design inspiration is largely stemming from MUMPS which provided a great ("oddly productive") combination of a database and a programming language. Being a constructor it's also a great tool for building applications with a better control over querying mechanics (since everything is actually described in PumpkinScript)
- tyingq 10y agoIt sounds sort of like "overlayfs" for data. Which might allow a non-destructive, no-copy way to... - Do what-if analysis. Change the price of oil at some point in history and see how your financials would have played out from that point forward. - Fork your database and have two live copies acting on different data or rules for a live comparison...without all the plumbing overhead. Perhaps having one set work with a fiscal year that is calendar year, and another with a different fiscal boundary.