-
-
Notes
-
-
-
- It is the user's responsibility to remove any operators,
- functions, aggregates, access methods, and tables that
- use a deleted domain.
-
-
-
-
-
Examples
for information on creating functions.
-
- No checks are made to ensure that types, operators, access
- methods, or triggers that rely on the function have been removed first.
-
destroyed, by using DELETE.
- If a table being destroyed has secondary indexes on it,
- they will be removed first. The removal of just a
- secondary index will not affect the contents of the underlying table.
-
- DROP TABLE will also remove any rules or triggers
- that exist for the target table.
+ DROP TABLE always removes any indexes, rules,
+ triggers, and constraints that exist for the target table. However,
+ to drop a table that is referenced by a foreign-key constraint of another
+ table, CASCADE must be specified. (CASCADE will remove the foreign-key
+ constraint, not the other table itself.)
Only the owner of a type can remove it.
-
-
-
Notes
-
-
-
- It is the user's responsibility to remove any operators,
- functions, aggregates, access methods, subtypes, and tables that
- use a deleted type. However, the associated array data type
- (which was automatically created by CREATE TYPE)
- will be removed automatically.
-
-
-
-
- If a built-in type is removed, the behavior of the server is
- unpredictable.
-
-
-
-
Examples