(no title)
shivasaxena | 6 months ago
Now that would be awesome!
EDIT: come to think of it, it would require going through CDC stream, and figuring out if any of the tables affected are a dependency of given materialized view. Maybe with some ast parsing as well to handle tenants/partitions. Sounds like it can work?
magicalhippo|6 months ago
At least on SQLAnywhere it seems to be implemented using triggers, ie not unlike what one would do if rolling your own.
lsuresh|6 months ago
4ndrewl|6 months ago
tanelpoder|6 months ago
https://oracle-base.com/articles/23/materialized-view-concur...
From the article: "Concurrent refreshes will only happen if there are no overlaps in the materialized view rows updated by each session."
cyanydeez|6 months ago