CS220: DATABASE SYSTEMS

BESE 12
OBJECTIVES

After completing this lesson, you should be able to

do the following:

 Describe each DML statement

 Insert rows into a table
 Update rows in a table
 Delete rows from a table
 Merge rows in a table
 Control transactions
MANIPULATING DATA
DATA MANIPULATION LANGUAGE

 A DML statement is executed when you:

 Add new rows to a table
 Modify existing rows in a table
 Remove existing rows from a table
 A transaction consists of a collection of DML statements
that form a logical unit of work.
ADDING A NEW ROW TO A TABLE
New
DEPARTMENTS row

…insert a new row

into the
DEPARMENTS
table…
THE INSERT STATEMENT SYNTAX

 Add new rows to a table by using the INSERT statement.

INSERT INTO table [(column [, column...])]

VALUES (value [, value...]);

 Only one row is inserted at a time with this syntax.

INSERTING NEW ROWS

 Insert a new row containing values for each column.

 List values in the default order of the columns in the
table.
 Optionally, list the columns in the INSERT clause.

INSERT INTO departments(department_id, department_name,

manager_id, location_id)
VALUES (70, 'Public Relations', 100, 1700);
1 row created.

 Enclose character and date values within single

quotation marks.
INSERTING ROWS WITH NULL VALUES

 Implicit method: Omit the column from the

column list.

INSERT INTO departments (department_id,

department_name )
VALUES (30, 'Purchasing');
1 row created.

• Explicit method: Specify the NULL keyword in the

VALUES clause.
INSERT INTO departments
VALUES (100, 'Finance', NULL, NULL);
1 row created.
INSERTING SPECIAL VALUES

The SYSDATE function records the current date

and time.
INSERT INTO employees (employee_id,
first_name, last_name,
email, phone_number,
hire_date, job_id, salary,
commission_pct, manager_id,
department_id)
VALUES (113,
'Louis', 'Popp',
'LPOPP', '515.124.4567',
SYSDATE, 'AC_ACCOUNT', 6900,
NULL, 205, 100);
1 row created.
INSERTING SPECIFIC DATE VALUES

 Add a new employee.

INSERT INTO employees
VALUES (114,
'Den', 'Raphealy',
'DRAPHEAL', '515.127.4561',
TO_DATE('FEB 3, 1999', 'MON DD, YYYY'),
'AC_ACCOUNT', 11000, NULL, 100, 30);
1 row created.
 Verify your addition.
COPYING ROWS
FROM ANOTHER TABLE

 Write your INSERT statement with a subquery.

INSERT INTO sales_reps(id, name, salary, commission_pct)

SELECT employee_id, last_name, salary, commission_pct
FROM employees
WHERE job_id LIKE '%REP%';

4 rows created.

 Do not use the VALUES clause.

 Match the number of columns in the INSERT clause to
those in the subquery.
CHANGING DATA IN A TABLE
EMPLOYEES

Update rows in the EMPLOYEES table.

THE UPDATE STATEMENT SYNTAX

 Modify existing rows with the UPDATE statement.

UPDATE table
SET column = value [, column = value, ...]
[WHERE condition];

 Update more than one row at a time, if required.

UPDATING ROWS IN A TABLE

 Specific row or rows are modified if you specify the

WHERE clause.
UPDATE employees
SET department_id = 70
WHERE employee_id = 113;
1 row updated.

 All rows in the table are modified if you omit the

WHERE clause.
UPDATE copy_emp
SET department_id = 110;
22 rows updated.
PROBLEM

Update employee 114’s job and

salary to match that of employee
205.

15
UPDATING TWO COLUMNS WITH A SUBQUERY

Update employee 114’s job and salary to match that of

employee 205.
UPDATE employees
SET job_id = (SELECT job_id
FROM employees
WHERE employee_id = 205),
salary = (SELECT salary
FROM employees
WHERE employee_id = 205)
WHERE employee_id = 114;
1 row updated.

Database Systems- 2012

PROBLEM
 Updates the COPY_EMP table based on the
values from the EMPLOYEES table. It changes
the department number of all employees with
employee 200’s job ID to employee 100’s
current department number.

17
UPDATING ROWS BASED
ON ANOTHER TABLE

Use subqueries in UPDATE statements to update

rows in a table based on values from another table.
UPDATE copy_emp
SET department_id = (SELECT department_id
FROM employees
WHERE employee_id = 100)
WHERE job_id = (SELECT job_id
FROM employees
WHERE employee_id = 200);
1 row updated.
UPDATING ROWS:
INTEGRITY CONSTRAINT ERROR

UPDATE employees
SET department_id = 55
WHERE department_id = 110;

UPDATE employees
*
ERROR at line 1:
ORA-02291: integrity constraint (HR.EMP_DEPT_FK)
violated - parent key not found
REMOVING A ROW FROM A TABLE

DEPARTMENTS

Delete a row from the DEPARTMENTS table.

THE DELETE STATEMENT

You can remove existing rows from a table by using

the DELETE statement.

DELETE [FROM] table

[WHERE condition];
DELETING ROWS FROM A TABLE

 Specific rows are deleted if you specify the WHERE clause.

DELETE FROM departments

WHERE department_name = 'Finance';
1 row deleted.

 All rows in the table are deleted if you omit the WHERE
clause.

DELETE FROM copy_emp;

22 rows deleted.
DELETING ROWS BASED ON ANOTHER TABLE

Use subqueries in DELETE statements to remove

rows from a table based on values from another table.
DELETE FROM employees
WHERE department_id =
(SELECT department_id
FROM departments
WHERE department_name LIKE '%Public%');
1 row deleted.
DELETING ROWS: INTEGRITY CONSTRAINT ERROR

DELETE FROM departments

WHERE department_id = 60;

DELETE FROM departments

*
ERROR at line 1:
ORA-02292: integrity constraint (HR.EMP_DEPT_FK)
violated - child record found
OVERVIEW OF THE EXPLICIT DEFAULT FEATURE

 With the explicit default feature, you can use the DEFAULT
keyword as a column value where the column default is
desired.
 The addition of this feature is for compliance with the SQL:
1999 Standard.
 This allows the user to control where and when the default
value should be applied to data.
 Explicit defaults can be used in INSERT and UPDATE
statements.
USING EXPLICIT DEFAULT VALUES

 DEFAULT with INSERT:

INSERT INTO departments
(department_id, department_name, manager_id)
VALUES (300, 'Engineering', DEFAULT);

 DEFAULT with UPDATE:

UPDATE departments
SET manager_id = DEFAULT WHERE department_id = 10;
THE MERGE STATEMENT

 Provides the ability to conditionally update or insert

data into a database table
 Performs an UPDATE if the row exists, and an INSERT
if it is a new row:
 Avoids separate updates
 Increases performance and ease of use
 Is useful in data warehousing applications
MERGING ROWS

Insert or update rows in the COPY_EMP table to match

the EMPLOYEES table.
MERGE INTO copy_emp c
USING employees e
ON (c.employee_id = e.employee_id)
WHEN MATCHED THEN
UPDATE SET
c.first_name = e.first_name,
c.last_name = e.last_name,
...
c.department_id = e.department_id
WHEN NOT MATCHED THEN
INSERT VALUES(e.employee_id, e.first_name, e.last_name,
e.email, e.phone_number, e.hire_date, e.job_id,
e.salary, e.commission_pct, e.manager_id,
e.department_id);
MERGING ROWS

SELECT *
FROM COPY_EMP;

no rows selected
MERGE INTO copy_emp c
USING employees e
ON (c.employee_id = e.employee_id)
WHEN MATCHED THEN
UPDATE SET
...
WHEN NOT MATCHED THEN
INSERT VALUES...;
SELECT *
FROM COPY_EMP;

20 rows selected.
DATABASE TRANSACTIONS

A database transaction consists of one of the

following:
 DML statements which constitute one consistent
change to the data
 One DDL statement
 One DCL statement
DATABASE TRANSACTIONS

 Begin when the first DML SQL statement is executed

 End with one of the following events:
 A COMMIT or ROLLBACK statement is issued
 A DDL or DCL statement executes (automatic commit)
 The user exits SQL*Plus
 The system crashes
ADVANTAGES OF COMMIT AND ROLLBACK STATEMENTS

With COMMIT and ROLLBACK statements, you can:

 Ensure data consistency
 Preview data changes before making changes
permanent
 Group logically related operations
CONTROLLING TRANSACTIONS
Time COMMIT
Transaction

DELETE

SAVEPOINT A
INSERT

UPDATE

SAVEPOINT B
INSERT
ROLLBACK ROLLBACK ROLLBACK
to SAVEPOINT B to SAVEPOINT A
ROLLING BACK CHANGES
TO A MARKER

 Create a marker in a current transaction by using the

SAVEPOINT statement.
 Roll back to that marker by using the ROLLBACK TO
SAVEPOINT statement.

UPDATE...
SAVEPOINT update_done;
Savepoint created.
INSERT...
ROLLBACK TO update_done;
Rollback complete.
IMPLICIT TRANSACTION PROCESSING

 An automatic commit occurs under the following

circumstances:
 DDL statement is issued
 DCL statement is issued
 Normal exit from SQL*Plus, without explicitly issuing
COMMIT or ROLLBACK statements
 An automatic rollback occurs under an abnormal
termination of SQL*Plus or a system failure.
STATE OF THE DATA
BEFORE COMMIT OR ROLLBACK

 The previous state of the data can be recovered.

 The current user can review the results of the DML operations
by using the SELECT statement.
 Other users cannot view the results of the DML statements by
the current user.
 The affected rows are locked; other users cannot change the
data within the affected rows.
STATE OF THE DATA AFTER COMMIT

 Data changes are made permanent in the database.

 The previous state of the data is permanently lost.
 All users can view the results.
 Locks on the affected rows are released; those rows are
available for other users to manipulate.
 All save points are erased.
COMMITTING DATA

 Make the changes.

DELETE FROM employees
WHERE employee_id = 99999;
1 row deleted.

INSERT INTO departments

VALUES (290, 'Corporate Tax', NULL, 1700);
1 row inserted.

 Commit the changes.

COMMIT;
Commit complete.
STATE OF THE DATA AFTER ROLLBACK

Discard all pending changes by using the ROLLBACK

statement:
 Data changes are undone.
 Previous state of the data is restored.
 Locks on the affected rows are released.

DELETE FROM copy_emp;

22 rows deleted.
ROLLBACK;
Rollback complete.
STATEMENT-LEVEL ROLLBACK

 If a single DML statement fails during execution, only

that statement is rolled back.
 The DB server implements an implicit savepoint.

 All other changes are retained.

 The user should terminate transactions explicitly by

executing a COMMIT or ROLLBACK statement.
READ CONSISTENCY

 Read consistency guarantees a consistent view of the

data at all times.
 Changes made by one user do not conflict with changes
made by another user.
 Read consistency ensures that on the same data:
 Readers do not wait for writers.
 Writers do not wait for readers.
IMPLEMENTATION OF READ CONSISTENCY

User A
UPDATE employees Data
SET salary = 7000 blocks
WHERE last_name = 'Goyal';

Rollback
segments

changed
SELECT * and unchanged
FROM userA.employees; Read data
consistent
image before
change
“old” data
User B
LOCKING

In a database, locks:
 Prevent destructive interaction between concurrent
transactions
 Require no user action

 Automatically use the lowest level of restrictiveness

 Are held for the duration of the transaction

 Are of two types: explicit locking and implicit locking

IMPLICIT LOCKING

 Two lock modes:

 Exclusive: Locks out other users
 Share: Allows other users to access
 High level of data concurrency:
 DML: Table share, row exclusive
 Queries: No locks required
 DDL: Protects object definitions
 Locks held until commit or rollback
SUMMARY

In this lesson, you should have learned how to use DML

statements and control transactions.
Statement Description

INSERT Adds a new row to the table

UPDATE Modifies existing rows in the table

DELETE Removes existing rows from the table

MERGE Conditionally inserts or updates data in a table

COMMIT Makes all pending changes permanent

SAVEPOINT Is used to rollback to the savepoint marker

ROLLBACK Discards all pending data changes

THANK YOU