May 2018
Intermediate to advanced
576 pages
30h 25m
English
The output of a materialized view is physically stored like a regular table, and the analogy doesn't stop here. In both cases, it is possible to create indexes to speed up queries.
A materialized view will not automatically change when its constituent tables change. For that to happen, you must issue the following:
REFRESH MATERIALIZED VIEW m_dish;
This replaces all the contents of the view with newly computed ones.
It is possible to quickly create an empty materialized view and populate it later. Just add WITH NO DATA at the end of the CREATE MATERIALIZED VIEW statement. Obviously, the view cannot be used before being populated, which you can do with REFRESH MATERIALIZED VIEW, as you just saw.
A materialized view cannot be ...