| Page Properties | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
- Views can simplify a complex table structure
- Views are acceptable when you want to restrict users to a particular subset of data.
- You can add/remove or concatenate fields easily in a view without modifying your underlying schema.
- Views can model complex joins easily.
...
What is a Materialized View
| Note |
|---|
Not currently supported in iShare as iShare uses PostgreSQL 9.0 - will be supported in iShare V6.0.0 which uses PostgreSQL 11. |
A materialized view is a database object that contains the results of a query. For example, it may be a local copy of data located remotely, or may be a subset of the rows and/or columns of a table or join result, or may be a summary using an aggregate function. In PostgreSQL, version 9.3 and newer natively support materialized views but they are not auto-refreshed. They are populated only at time of creation (unless WITH NO DATA is used). It may be refreshed later manually using REFRESH MATERIALIZED VIEW. From version 9.4, the refresh may be concurrent with selects on the materialized view if CONCURRENTLY is used.