USING DDL STATEMENTS

TO CREATE AND MANAGE

TABLES
OBJECTIVES
 After completing this lesson, you should be able to do
the following:
 Categorize the main database objects
 Review the table structure
 List the data types that are available for columns
 Create a simple table
 Explain how constraints are created at the time of table
creation
 Describe how schema objects work
LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
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 name to an object

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
LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
CREATE TABLE STATEMENT
 You must have:
 CREATE TABLE privilege
 A storage area

CREATE TABLE [schema.]table

(column datatype [DEFAULT expr][, ...]);
 You specify:
 Table name
 Column name, column data type, and column size
REFERENCING ANOTHER USER’S
TABLES
 Tablesbelonging to other users are not in the user’s schema.
 You should use the owner’s name as a prefix to those tables.

USERA USERB
SELECT * SELECT *
FROM userB.employees; FROM userA.employees;
DEFAULT OPTION
 Specify a default value for a column during an insert.

... hire_date DATE DEFAULT SYSDATE, ...

 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.

CREATE TABLE hire_dates

(id NUMBER(8),
hire_date DATE DEFAULT SYSDATE);
CREATING TABLES
 Create the table:
CREATE TABLE dept
(deptno NUMBER(2),
dname VARCHAR2(14),
loc VARCHAR2(13),
create_date DATE DEFAULT SYSDATE);

 Confirm table creation:

DESCRIBE dept
LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
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 binary data
RAW
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 Stored as an interval of years
MONTH and months
INTERVAL DAY TO Stored as an interval of days, hours, minutes,
SECOND and seconds
LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
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 creation of the table
 After the creation of the table

 Define a constraint at the column or table level.

 View a constraint in the data dictionary.
DEFINING CONSTRAINTS
 Syntax:

CREATE TABLE [schema.]table

(column datatype [DEFAULT expr]
[column_constraint],
...
[table_constraint][,...]);
 Column-level constraint syntax:
column [CONSTRAINT constraint_name] constraint_type,
 Table-level constraint syntax:
column,...
[CONSTRAINT constraint_name] constraint_type
(column, ...),
DEFINING CONSTRAINTS
 Example of a column-level constraint:
CREATE TABLE employees(
employee_id NUMBER(6)
CONSTRAINT emp_emp_id_pk PRIMARY KEY, 1
first_name VARCHAR2(20),
...);
 Example of a table-level constraint:
CREATE TABLE employees(
employee_id NUMBER(6),
first_name VARCHAR2(20),
... 2
job_id VARCHAR2(10) NOT NULL,
CONSTRAINT emp_emp_id_pk
PRIMARY KEY (EMPLOYEE_ID));
NOT NULL CONSTRAINT
 Ensures that null values are not permitted for the column:

…
NOT NULL constraint Absence of NOT NULL
(Primary Key enforces NOT NULL constraint (Any row can
NOT NULL constraint.) constraint contain a null value for
this column.)
UNIQUE CONSTRAINT
UNIQUE constraint
EMPLOYEES

…
INSERT INTO
Allowed
Not allowed:
already exists
UNIQUE CONSTRAINT
 Defined at either the table level or the column level:

CREATE TABLE employees(

employee_id NUMBER(6),
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

Not allowed INSERT INTO

(null value)

Not allowed
(50 already exists)
 KEY CONSTRAINT
FOREIGNDEPARTMENTS
PRIMARY
KEY

…
EMPLOYEES
FOREIGN
KEY

…
INSERT INTO Not allowed
(9 does not
exist)
Allowed
FOREIGN KEY CONSTRAINT
 Defined at either the table level or the column level:

CREATE TABLE employees(

employee_id NUMBER(6),
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:
CREATE TABLE EXAMPLE
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)
CONSTRAINT emp_manager_fk REFERENCES
employees (employee_id)
, department_id NUMBER(4)
CONSTRAINT emp_dept_fk REFERENCES
departments (department_id));
VIOLATING CONSTRAINTS

UPDATE employees
SET department_id = 55
WHERE department_id = 110;

 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

WHERE department_id = 60;
LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
CREATING A TABLE
USING A SUBQUERY
 Create a table and insert rows by combining the CREATE TABLE
statement and the AS subquery option.
CREATE TABLE table
[(column, column...)]
AS subquery;
 Match the number of specified columns to the number of
subquery columns.
 Define columns with column names and default values.
CREATING A TABLE
USING A SUBQUERY

CREATE TABLE dept80

AS
SELECT employee_id, last_name,
salary*12 ANNSAL,
hire_date
FROM employees
WHERE department_id = 80;

DESCRIBE dept80
LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
ALTER TABLE STATEMENT
 Use the ALTER TABLE statement to:
 Add a new column
 Modify an existing column definition
 Define a default value for the new column
 Drop a column
 Rename a column
 Change table to read-only status
READ-ONLY TABLES
 Use the ALTER TABLE syntax to put a table into the read-only
mode:
 PreventsDDL or DML changes during table maintenance
 Change it back into read/write mode

ALTER TABLE employees READ ONLY;

-- perform table maintenance and then

-- return table back to read/write mode

ALTER TABLE employees READ WRITE;

LESSON AGENDA
 Database objects
 Naming rules
 CREATE TABLE statement:
 Access another user’s tables
 DEFAULT option

 Data types
 Overview of constraints: NOT NULL, PRIMARY KEY, FOREIGN
KEY, CHECK constraints
 Creating a table using a subquery
 ALTER TABLE
 Read-only tables
 DROP TABLE statement
DROPPING A TABLE
 Moves a table to the recycle bin
 Removes the table and all its data entirely if the PURGE clause is
specified
 Invalidates dependent objects and removes object privileges on
the table

DROP TABLE dept80;

SUMMARY
 In this lesson, you should have learned how to use the
CREATE TABLE statement to create a table and include
constraints:
 Categorize the main database objects
 Review the table structure
 List the data types that are available for columns
 Create a simple table
 Explain how constraints are created at the time of table creation
 Describe how schema objects work
PRACTICE 10: OVERVIEW
 This practice covers the following topics:
 Creating new tables
 Creating a new table by using the CREATE TABLE AS syntax
 Verifying that tables exist
 Setting a table to read-only status
 Dropping tables