ALTER VIEW
Modifies the metadata of an existing view. The changes are auto-committed
Syntax
ALTER VIEW [[database.]schema.]view { ... | OWNER TO owner ... | SET SCHEMA schema ... | { INCLUDE | EXCLUDE | MATERIALIZE } [ SCHEMA ] PRIVILEGES
ALTER VIEW [[database.]schema.]view[,…] RENAME TO new-view-name[,…]
Parameters
[database.]schema
|
Specifies a schema, by default myschema.thisDbObject If you specify a database, it must be the current database. |
view |
The view to alter. |
SET SCHEMA schema
|
Moves the view from one schema to another. |
OWNER TO owner
|
Changes the view owner. |
{ INCLUDE
|
Specifies default inheritance of schema privileges for this view:
Note: If inherited privileges are disabled at the database level, schema privileges can still be materialized. See also Setting Privileges Inheritance on Tables and Views in the Administrator's Guide. |
RENAME TO
|
Renames one or more views: RENAME TO new‑view‑name[,…]
The following requirements apply:
|
Privileges
Changing a view requires the following privileges:
- Superuser
- If renaming a view, CREATE privileges on the schema in which the view is renamed.
Example
The following command renames view1
to view2
:
=> CREATE VIEW view1 AS SELECT * FROM t; CREATE VIEW => ALTER VIEW view1 RENAME TO view2; ALTER VIEW