mirror of
https://github.com/aljazceru/turso.git
synced 2026-01-06 09:44:21 +01:00
05b275f865
min/max require O(N) storage because of deletions. It is easy to see why: if you *add* a new row, you can quickly and incrementally check if it is smaller / larger than the previous accumulator. But when you *delete* a row you can't do that and have to check the previous values. Feldera uses something called "traces" which to me look a lot like indexes. When we implement materialization, this is easy to do. But to avoid having something broken, we'll just disable min / max until then.