Is it possible for Incorta to issue a warning when a developer attempts to save a materialized view that has improperly joined tables? I have attached a screenshot to demonstrate the issue. Such actions can cause a Cartesian product of several billion rows, which negatively impacts not only the performance of the affected MV but also the other MVs running concurrently in the system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.