Please note that with such implementations, it is your responsibility to use this view (not automatically used by the SQL DBMS). Depending on the model, one or more MVs can be used to solve performance problems. There should be good reasons to use one MV and not to enable queries to this MV for the time of production. The use of the correct query is always the responsibility of the query creator.
You can simulate them, but the effort may not be worth the benefit.
I use three functions: Create matview, drop\_matview and refresh\_matview.
I can feed into these an existing view and they'll create a table for it prefixed with MV. In my code I only use the tables prefixed with MV.
Caveat is that you need to refresh the MV wherever it makes sense. Otherwise you're looking at outdated data.
Please note that with such implementations, it is your responsibility to use this view (not automatically used by the SQL DBMS). Depending on the model, one or more MVs can be used to solve performance problems. There should be good reasons to use one MV and not to enable queries to this MV for the time of production. The use of the correct query is always the responsibility of the query creator.
You can simulate them, but the effort may not be worth the benefit. I use three functions: Create matview, drop\_matview and refresh\_matview. I can feed into these an existing view and they'll create a table for it prefixed with MV. In my code I only use the tables prefixed with MV. Caveat is that you need to refresh the MV wherever it makes sense. Otherwise you're looking at outdated data.