Using ddl statements to create and manage tables

Using DDL Statements
to Create and Manage
Tables

Database Objects
Object Description
Table Basic unit of storage; composed of rows
View Logically represents subsets of data from
one or more tables
Sequence Generates numeric values
Index Improves the performance of some
queries
Synonym Gives alternative names to objects

Naming Rules
• Table names and column names:
• Must begin with a letter
• Must be 1–30 characters long
• Must contain only A–Z, a–z, 0–9, _, $, and #
• Must not duplicate the name of another object owned by the same
user
• Must not be an Oracle server reserved word

CREATE TABLE Statement
• You must have:
• CREATE TABLE privilege
• A storage area
• You specify:
• Table name
• Column name, column data type, and column size
CREATE TABLE [schema.]table
(column datatype [DEFAULT expr][, ...]);

Referencing Another User’s Tables
• Tables belonging to other users are not in the user’s schema.
• You should use the owner’s name as a prefix to those tables.
USERBUSERA
SELECT *
FROM userB.employees;
SELECT *
FROM userA.employees;

DEFAULT Option
• Specify a default value for a column during an insert.
• Literal values, expressions, or SQL functions are legal values.
• Another column’s name or a pseudocolumn are illegal values.
• The default data type must match the column data type.
... hire_date DATE DEFAULT SYSDATE, ...
CREATE TABLE hire_dates
(id NUMBER(8),
hire_date DATE DEFAULT SYSDATE);
Table created.

Creating Tables
• Create the table.
• Confirm table creation.
DESCRIBE dept
CREATE TABLE dept
(deptno NUMBER(2),
dname VARCHAR2(14),
loc VARCHAR2(13),
create_date DATE DEFAULT SYSDATE);
Table created.

Data Types
Data Type Description
VARCHAR2(size) Variable-length character data
CHAR(size) Fixed-length character data
NUMBER(p,s) Variable-length numeric data
DATE Date and time values
LONG Variable-length character data (up to 2 GB)
CLOB Character data (up to 4 GB)
RAW and LONG
RAW
Raw binary data
BLOB Binary data (up to 4 GB)
BFILE Binary data stored in an external file (up to 4 GB)
ROWID A base-64 number system representing the unique
address of a row in its table

Datetime Data Types
• You can use several datetime data types:
Data Type Description
TIMESTAMP Date with fractional seconds
INTERVAL YEAR TO
MONTH
Stored as an interval of years
and months
INTERVAL DAY TO
SECOND
Stored as an interval of days, hours,
minutes, and seconds

Datetime Data Types
• The TIMESTAMP data type is an extension of the DATE data type.
• It stores the year, month, and day of the DATE data type plus hour,
minute, and second values as well as the fractional second value.
• You can optionally specify the time zone.
TIMESTAMP[(fractional_seconds_precision)]
WITH TIME ZONE
WITH LOCAL TIME ZONE

Datetime Data Types
• The INTERVAL YEAR TO MONTH data type stores a period of time
using the YEAR and MONTH datetime fields:
• The INTERVAL DAY TO SECOND data type stores a period of time
in terms of days, hours, minutes, and seconds:
INTERVAL YEAR [(year_precision)] TO MONTH
INTERVAL DAY [(day_precision)]
TO SECOND [(fractional_seconds_precision)]

Including Constraints
• Constraints enforce rules at the table level.
• Constraints prevent the deletion of a table if there are dependencies.
• The following constraint types are valid:
• NOT NULL
• UNIQUE
• PRIMARY KEY
• FOREIGN KEY
• CHECK

Constraint Guidelines
• You can name a constraint, or the Oracle server generates a name by
using the SYS_Cn format.
• Create a constraint at either of the following times:
• At the same time as the table is created
• After the table has been created
• Define a constraint at the column or table level.
• View a constraint in the data dictionary.

Defining Constraints
• Syntax:
• Column-level constraint:
• Table-level constraint:
CREATE TABLE [schema.]table
(column datatype [DEFAULT expr]
[column_constraint],
...
[table_constraint][,...]);
column,...
[CONSTRAINT constraint_name] constraint_type
(column, ...),
column [CONSTRAINT constraint_name] constraint_type,

Defining Constraints
• Column-level constraint:
• Table-level constraint:
CREATE TABLE employees(
employee_id NUMBER(6)
CONSTRAINT emp_emp_id_pk PRIMARY KEY,
first_name VARCHAR2(20),
...);
employee_id NUMBER(6),
first_name VARCHAR2(20),
...
job_id VARCHAR2(10) NOT NULL,
CONSTRAINT emp_emp_id_pk
PRIMARY KEY (EMPLOYEE_ID));
1
2

NOT NULL Constraint
• Ensures that null values are not permitted for the column:
NOT NULL constraint
(No row can contain
a null value for
this column.)
Absence of NOT NULL
constraint
(Any row can contain a
null value for this
column.)
NOT NULL
constraint
…

UNIQUE Constraint
EMPLOYEES
UNIQUE constraint
INSERT INTO
Not allowed:
already exists
Allowed
…

UNIQUE Constraint
• Defined at either the table level or the column level:
last_name VARCHAR2(25) NOT NULL,
email VARCHAR2(25),
salary NUMBER(8,2),
commission_pct NUMBER(2,2),
hire_date DATE NOT NULL,
...
CONSTRAINT emp_email_uk UNIQUE(email));

PRIMARY KEY Constraint
DEPARTMENTS
PRIMARY KEY
INSERT INTONot allowed
(null value)
Not allowed
(50 already exists)
…

FOREIGN KEY ConstraintDEPARTMENTS
EMPLOYEES
FOREIGN
KEY
INSERT INTO
Not allowed
(9 does not
exist)
Allowed
PRIMARY
KEY
…
…

FOREIGN KEY Constraint
• Defined at either the table level or the column level:
last_name VARCHAR2(25) NOT NULL,
email VARCHAR2(25),
salary NUMBER(8,2),
commission_pct NUMBER(2,2),
hire_date DATE NOT NULL,
...
department_id NUMBER(4),
CONSTRAINT emp_dept_fk FOREIGN KEY (department_id)
REFERENCES departments(department_id),
CONSTRAINT emp_email_uk UNIQUE(email));

FOREIGN KEY Constraint:
Keywords
• FOREIGN KEY: Defines the column in the child
table at the table-constraint level
• REFERENCES: Identifies the table and column in the
parent table
• ON DELETE CASCADE: Deletes the dependent
rows in the child table when a row in the parent table
is deleted
• ON DELETE SET NULL: Converts dependent
foreign key values to null

CHECK Constraint
• Defines a condition that each row must satisfy
• The following expressions are not allowed:
• References to CURRVAL, NEXTVAL, LEVEL, and ROWNUM pseudocolumns
• Calls to SYSDATE, UID, USER, and USERENV functions
• Queries that refer to other values in other rows
..., salary NUMBER(2)
CONSTRAINT emp_salary_min
CHECK (salary > 0),...

CREATE TABLE: Example
CREATE TABLE employees
( employee_id NUMBER(6)
CONSTRAINT emp_employee_id PRIMARY KEY
, first_name VARCHAR2(20)
, last_name VARCHAR2(25)
CONSTRAINT emp_last_name_nn NOT NULL
, email VARCHAR2(25)
CONSTRAINT emp_email_nn NOT NULL
CONSTRAINT emp_email_uk UNIQUE
, phone_number VARCHAR2(20)
, hire_date DATE
CONSTRAINT emp_hire_date_nn NOT NULL
, job_id VARCHAR2(10)
CONSTRAINT emp_job_nn NOT NULL
, salary NUMBER(8,2)
CONSTRAINT emp_salary_ck CHECK (salary>0)
, commission_pct NUMBER(2,2)
, manager_id NUMBER(6)
, department_id NUMBER(4)
CONSTRAINT emp_dept_fk REFERENCES
departments (department_id));

UPDATE employees
*
ERROR at line 1:
ORA-02291: integrity constraint (HR.EMP_DEPT_FK)
violated - parent key not found
UPDATE employees
SET department_id = 55
WHERE department_id = 110;
Violating Constraints
• Department 55 does not exist.

Violating Constraints
• You cannot delete a row that contains a primary key that is used as a
foreign key in another table.
DELETE FROM departments
DELETE FROM departments
*
ERROR at line 1:
ORA-02292: integrity constraint (HR.EMP_DEPT_FK)
violated - child record found

Creating a Table
by Using a Subquery
• Create a table and insert rows by combining the CREATE TABLE
statement and the AS subquery option.
• Match the number of specified columns to the number of subquery
columns.
• Define columns with column names and
default values.
CREATE TABLE table
[(column, column...)]
AS subquery;

CREATE TABLE dept80
AS
SELECT employee_id, last_name,
salary*12 ANNSAL,
hire_date
FROM employees
Table created.
Creating a Table
by Using a Subquery
DESCRIBE dept80

ALTER TABLE Statement
• Use the ALTER TABLE statement to:
• Add a new column
• Modify an existing column
• Define a default value for the new column
• Drop a column

Dropping a Table
• All data and structure in the table are deleted.
• Any pending transactions are committed.
• All indexes are dropped.
• All constraints are dropped.
• You cannot roll back the DROP TABLE statement.
DROP TABLE dept80;
Table dropped.

Using ddl statements to create and manage tables

Recommended

More Related Content

What's hot (20)

Similar to Using ddl statements to create and manage tables (20)

More from Syed Zaid Irshad (20)

Recently uploaded (20)

Using ddl statements to create and manage tables

Editor's Notes