1.0

Table Of Contents
Example
DROP SCHEMA EMP RESTRICT
The EMP schema may only be deleted from the database if no objects are dened in the
EMP schema.
DROP TABLE
Remove the specied table.
Syntax
DROP TABLE [IF EXISTS] [schema-name.]table-name
Description
Removes the specied table. Include the IF EXISTS clause to execute the statement only if the specied table
exists in SQLFire. The schema-name. prex is optional if you are currently using the schema that contains the
table.
Note: Triggers, constraints (primary, unique, check and references from the table being dropped) and
indexes on the table are silently dropped. Dropping a table invalidates statements that depend on the table.
DROP TRIGGER
Remove the specied trigger.
Syntax
DROP TRIGGER trigger-name
Description
Removes the specied trigger.
Note: When a table is dropped, all triggers on that table are automatically dropped i.e. a table's triggers
needn't be explicitly dropped before dropping the table
DROP TYPE
The DROP TYPE statement removes a user-dened type (UDT) that was created using a CREATE TYPE on
page 467.
Syntax
DROP TYPE [ schema-name. ] SQL92Identifier RESTRICT
The type name is composed of an optional schemaName and a SQL92Identier. If a schemaName is not provided,
the current schema is the default schema. If a qualied type name is specied, the schema name cannot begin
with SYS.
The RESTRICT keyword is required. CASCADE semantics are not supported. That is, SQLFire will not track
down and drop orphaned objects.
Dropping a UDT implicitly drops all USAGE privileges that reference it.
You cannot drop a type if it would make another SQL object unusable. This includes the following restrictions:
Table columns: No table columns have this UDT.
477
SQL Language Reference