3 ms·
The OP briefly alludes to the big difference: differential dataflow. My understanding is that it means that the database doesn't update the view simply because
by jacques_chester 6y ago
The OP briefly alludes to the big difference: differential dataflow.
My understanding is that it means that the database doesn't update the view simply because a datum arrived, but rather only if the datum will change it. That avoids an enormous amount of churn and makes materialized views fantastically cheaper on average.
Edit: The original thread here on HN has lots of detailed answers from the Materialize folks, plus some gushing fandom from that jacques_chester dweeb: https://news.ycombinator.com/item?id=22359769 https://news.ycombinator.com/item?id=22359769
- rst 6y agoThat's what Oracle FAST REFRESH does as well, in the limited cases where it works. Which is why a comparison to Materialize would be intersting...
- arjunnarayan 6y agoI think a 5-second summary of the difference is that Materialize is Oracle FAST REFRESH for almost* all of SQL, as opposed to just those very limited cases where Oracle's FAST REFRESH works. Oracle's docs have entire features in order to help you diagnose whether your views are eligible for fast or synchronous refresh[1]. In Materialize, everything you can express in SQL is fast refreshed. No caveats. [1] https://docs.oracle.com/database/121/DWHSG/sync.htm#DWHSG9146 https://docs.oracle.com/database/121/DWHSG/sync.htm#DWHSG914... *Almost, because the surface area is truly astonishing.