CREATE TABLE problems: Table already exists.

CREATE TABLE problems: Table already exists.

schema:scott

When developing table definitions it may be useful to precede a sequence of CREATE TABLE statements with the corresponding DROP TABLE statements in the reverse order (see next tip).

CREATE TABLE t_holiday (a INTEGER)

CREATE TABLE IF NOT EXISTS
 t_holiday(a INTEGER)

Does nothing if the table is already there.

CREATE OR REPLACE will remove an old VIEW exists. It does not work with a TABLE :(

CREATE and DROP Operations

CREATE a new table

DROP a table

Composite primary key

CREATE a foreign key

CREATE a VIEW

Autonumber fields

ALTER TABLE ... ADD COLUMN

ALTER TABLE ... DROP COLUMN

ALTER TABLE ... ADD constraint

CREATE TABLE problems: Invalid column name.

CREATE TABLE problems: Insufficient privileges.

CREATE TABLE problems: Table already exists.

DROP TABLE problems: Foreign key references.

CREATE TABLE problems: Foreign key references.

Rename column