Oracle SQL PL SQL A Brief Introduction
Oracle SQL PL SQL A Brief Introduction
to
Oracle SQL/PL-SQL
Prepared for
CSE 304 (Database Sessional) Course
Dept. of CSE, BUET
Author
Sukarna Barua
Assistant Professor
Dept. of CSE
Bangladesh University of Engineering and Technology (BUET)
Dhaka-1000, Bangaldesh.
Contents
Chapter 1: Introduction ................................................................................................................................ 8
Introduction ...................................................................................................................................... 8
1.
1.
2.
3.
ORDER BY Clause................................................................................................................................. 22
Practice 2.3.......................................................................................................................................... 23
4.
Page 1
1.
2.
3.
4.
NVL function........................................................................................................................................ 30
Practice 3.4.......................................................................................................................................... 31
Data Type Conversion Functions .................................................................................................... 31
5.
6.
1.
3.
4.
1.
1.
2.
1.
Set operators....................................................................................................................................... 56
UNION and UNION ALL operators....................................................................................................... 57
INTERSECT operator ............................................................................................................................ 57
MINUS operator .................................................................................................................................. 58
Use of conversion functions in set operations ................................................................................... 58
Practice 7.1.......................................................................................................................................... 59
More Practice Problems.................................................................................................................. 59
2.
1.
2.
3.
4.
1.
2.
Constraints .......................................................................................................................................... 71
Defining constraints ............................................................................................................................ 72
FOREIGN KEY constraint...................................................................................................................... 74
CHECK constraints ............................................................................................................................... 75
Deleting Tables from Database ....................................................................................................... 76
3.
5.
1.
2.
3.
What is an Index.................................................................................................................................. 81
CREATE INDEX statement ................................................................................................................... 81
When to create indexes? .................................................................................................................... 82
4.
Page 5
1.
2.
3.
4.
5.
6.
Page 7
Chapter 1: Introduction
1. Introduction
What is SQL
Structured Query Language (SQL) is the language used to interaction with a database management
system. The language defines the statements for retrieving data from the database, updating data in the
database, inserting data into the database, and more similar things.
SQL is the way by which all programs and users access data in an Oracle database. SQL provides
statements for a variety of tasks including:
Querying data
SQL Statements
All SQL statements supported by Oracle database can be grouped in several categories as illustrated in
following table:
SQL statement
SELECT
INSERT
UPDATE
in database
DELETE
CREATE
ALTER
DROP
COMMIT
ROLLBACK
Page 8
SQL * PLUS This is a command line tool and is the most popular tool
SQL Developer This is a graphical tool used by Oracle users to interact with Oracle database.
Navicat This is a third party tool that is used to connect to several databases such as Oracle,
MySQL, etc. This is one of the most popular GUI tools to interact with database.
The HR schema
The Human Resource (HR) schema is a part of Oracle sample database that can be installed with Oracle.
This course uses the tables in HR schema for all practice and homework sessions. The schema contains
the following tables:
REGIONS contain rows that represent a region such as America, Asia, and so on.
COUNTRIES contain rows for countries each of which is associated with a region
LOCATIONS contains the specific address of a specific office, warehouse, or a production site
of a company in a particular country
EMPLOYEES contain detail about each employee working for a department. Some employees
may not be assigned to any department.
JOBS contain the job types that can be held by each employee.
JOB_HISTORY contain the job history of the employees. If an employee changes department
within a job, or changes a job within a department, a new row is inserted in this table with the
earlier job information of the employee.
The following table shows the column names for all tables in HR schema.
Table Name
Column Names
REGIONS
REGION_ID, REGION_NAME
COUNTRIES
LOCATIONS
Page 9
STATE_PROVINCE, COUNTRY_ID
DEPARTMENTS
EMPLOYEES
JOB_HISTORY
JOBS
Page 10
For example, the following SELECT statement retrieves some data from EMPLOYEES table.
SELECT EMPLOYEE_ID, LAST_NAME, SALARY
FROM EMPLOYEES ;
If you want select values of all columns you can either specify all column names or specify a * as
follows:
SELECT * FROM EMPLOYEES ;
Page 11
You can use arithmetic expressions involving addition, subtraction, multiplication, and division as shown
in following SELECT statements.
SELECT EMPLOYEE_ID, LAST_NAME, SALARY*12
FROM EMPLOYEES ;
SELECT EMPLOYEE_ID, LAST_NAME, SALARY+12
FROM EMPLOYEES ;
SELECT EMPLOYEE_ID, LAST_NAME, (SALARY-1000)*5
FROM EMPLOYEES ;
SELECT EMPLOYEE_ID, LAST_NAME, (SALARY + SALARY*0.15) / 1000
FROM EMPLOYEES ;
The column alias should be double quoted if it contains spaces as shown below:
SELECT EMPLOYEE_ID, LAST_NAME, SALARY*12 "ANNUAL SALARY"
FROM EMPLOYEES ;
All SQL statements have a terminator, i.e., semicolon (;) at the end
SQL Keywords are not case-sensitive, e.g., SELECT, Select, and select are all same.
Page 12
NULL value is not same as zero value or some other specific value, it is simply unknown
Execute the following SELECT statement and search through the values of COMMISSION_PCT column
in the output. You will notice that there are many NULL, i.e., empty values there.
SELECT LAST_NAME, COMMISSION_PCT
FROM EMPLOYEES ;
The following example illustrate that when a column value is NULL, then arithmetic expression also
outputs NULL. You will notice that SALCOMM column in the output is null in those rows where either
SALARY value is NULL or COMMISSION_PCT value is NULL.
SELECT LAST_NAME, (SALARY+SALARY*COMMISSION_PCT) SALCOMM
FROM EMPLOYEES ;
You can also add additional texts with the column values as the following statement does.
Page 13
SELECT ('NAME is: ' || FIRST_NAME || ' ' || LAST_NAME) FULLNAME, SALARY
FROM EMPLOYEES ;
Note the use of single quotes in the above statement. The single quote is used to mean text values. This is
necessary and without the single quote, Oracle will think the text as a column name, which is definitely
wrong in this case. So, you must use single quote around text values (not around column names).
However, no quote is used for numeric values, e.g., 350, and 7777.
You will notice that, the output contains similar, i.e., duplicate values since several rows (employees)
have the same JOB_ID in the EMPLOYEES table. You can remove the duplicate outputs by using the
DISTINCT keyword as shown below.
SELECT DISTINCT JOB_ID
FROM EMPLOYEES ;
In the above SELECT, output will contain unique values of JOB_ID therefore removing duplicate
outputs. The DISTINCT Keyword works on all columns specified in the SELECT and outputs unique
rows (removes duplicate rows).
SELECT DISTINCT DEPARTMENT_ID, JOB_ID
FROM EMPLOYEES ;
Page 14
DESCRIBE EMPLOYEES ;
The basic data types used in Oracle are given in following table.
Data Type
Description
NUMBER
VARCHAR2(size)
CHAR(size)
DATE
Practice 2.1
a. Write an SQL query to retrieve all country names.
b. Write an SQL query to retrieve all job titles.
c. Write an SQL query to retrieve all MANAGER_IDs.
d. Write an SQL query to retrieve all city names. Remove duplicate outputs.
e. Write an SQL query to retrieve LOCATION_ID, ADDRESS from LOCATIONS table. The
ADDRESS should print each location in the following format: STREET_ADDRESS, CITY,
STATE_PROVINCE, POSTAL_CODE.
Page 15
SELECT
FROM table_name
WHERE condition ;
For example, the following SELECT retrieves last names and salaries of those employees only whose
DEPARTMENT_ID column value is 80.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE DEPARTMENT_ID = 80 ;
The following example shows conditions involving text and date values.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME = 'Whalen' ;
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE HIRE_DATE =
'01-JAN-1995' ;
Note that use of single quotes around text data and date data (01-JAN-1995). The date text given in the
query is in default format. Until, you learn TO_DATE conversion function in later chapters, you will need
to enter data values in this way in default format. Otherwise, Oracle may generate error messages.
Description
Equal to
Page 16
>
Greater than
>=
<
Less than
<=
<>
Not equal to
value
IN (value1, value2, )
LIKE
IS NULL
Is a NULL value
Page 17
Three or more conditions can be joined. In such cases, parenthesis should be used to clarify the execution
order and combination of the conditions.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE DEPARTMENT_ID <> 80 AND
(SALARY > 5000 OR COMMISSION_PCT IS NOT NULL)
Note the difference in outputs of the above two statements. The use of parenthesis change the order of
execution of the operators, therefore changes meaning and output of the SELECT statements.
Page 18
Note the use of special symbol (%) above. The % means zero or more characters. A % before s
means zero or more characters can precede the s, a % after s means zero or more characters can
follow s. To understand the position of % and resultant effect, observe the outputs of the following
queries.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME LIKE 'S%' ;
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME LIKE '%s' ;
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME LIKE 's' ;
If you execute the above three statements and observe the output, you will note that
The first statement retrieves those rows where LAST_NAME starts with a S. Any number of
any characters can follow after the S. Note that text match is case-sensitive, hence S% and
s% are not same.
The second statement retrieves those rows where LAST_NAME ends with s. Any number of
any characters can precede the s. Only the last character must be s.
Page 19
The third statement retrieves those rows where LAST_NAME is exactly s (like the = operator)
Like the % special symbol, the _ special symbol is used to match exactly one character. For example,
execute the following statements and observe the outputs.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME LIKE 'a_' ;
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME LIKE '_ _ b' ;
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE LAST_NAME LIKE '_%' ;
If you execute the above three statements and observe the output, you will note that
The first statement retrieves those rows where LAST_NAME contains exactly two characters
where the first character must be a, e.g., ab, ak, and ac.
The second statement retrieves those rows where LAST_NAME contains exactly three characters
in which the last one must be b
The third statement retrieves those rows where LAST_NAME contains at least one character, i.e.,
last name cannot be empty text
0.20 ;
The above statement retrieves records of those employees whose COMMISSION_PCT value is less than
0.20. The query should retrieve those rows that have NULL values in COMMISSION_PCT column,
Page 20
because NULL should mean a 0 value in most cases. However, Oracle would not retrieve those rows.
This is because; comparison with NULL is regarded as FALSE (not matched). If you want to retrieve
records with NULL values also, then you have to use IS NULL comparison operator as shown below.
SELECT LAST_NAME, SALARY, COMMISSION_PCT
FROM EMPLOYEES
WHERE COMMISSION_PCT < 0.20 OR COMMISSION_PCT IS NULL ;
A common mistake is using equality (=) operator to retrieve records with NULL values as shown below.
But, the query will retrieve no rows as the equality comparison fails due to NULL value.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE COMMISSION_PCT = NULL ;
Practice 2.2
a. Select names of all employees who have joined before January 01, 1998.
b. Select all locations in the following countries: Canada, Germany, United Kingdom.
c. Select first names of all employees who do not get any commission.
d. Select first names of employees whose last name starts with an 'a'.
e. Select first names of employees whose last name starts with an 's' and ends with an 'n'.
f.
g. Select all names of employees whose job type is 'AD_PRES' and whose salary is at least
23000.
h. Select names of all employees whose last name do not contain the character 's'.
i.
Select names and COMMISSION_PCT of all employees whose commission is at most 0.30.
j.
Select names of all employees who have joined after January 01, 1998.
k. Select names of all employees who have joined in the year 1998.
Page 21
The ORDER BY clause is used after the WHERE clause to specify sorting order. The following statement
retrieves records of employees and sorts the output in descending order of SALARY values.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
ORDER BY SALARY DESC ;
SELECT LAST_NAME, SALARY, HIRE_DATE
FROM EMPLOYEES
ORDER BY HIRE_DATE ASC ;
Outputs can be sorted based on multiple columns. So, if the first column is equal for multiple rows, then
the rows are sorted according to the second column. If the second column is also same, then rows are
sorted based on third column, and so on. The following statement illustrates such queries.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
ORDER BY SALARY DESC, LAST_NAME ASC ;
You can use column alias in ordering results. The following examples illustrate this.
SELECT JOB_TITLE, (MAX_SALARY - MAX_SALARY) DIFF_SALARY
FROM JOBS
ORDER BY DIFF_SALARY DESC ;
Page 22
Practice 2.3
a. Select names, salary, and commissions of all employees of job type 'AD_PRES'. Sort the
result in ascending order of commission and then descending order of salary.
b. Retrieve all country names in lexicographical ascending order.
Page 23
Description
LOWER (text)
Converts the text to all lowercase. Here, text can be column name or an
expression.
UPPER (text)
Converts the text to all uppercase. Here, text can be column name or an
expression.
INITCAP (text)
Converts the first character of the text to uppercase. Here, text can be
column name or an expression.
The following table shows the outputs of applying case conversion functions on the text hello WORLD.
Function
Output
LOWER(hello WORLD)
hello world
UPPER(hello WORLD)
HELLO WORLD
INITCAP(hello WORLD)
Hello world
The following statement shows the use case-conversion functions in SELECT statements.
SELECT (INITCAP(FIRST_NAME) ||
FROM EMPLOYEES ;
Note the use of three functions in the above statement. The column aliases are good ways to redefine
column headers.
Page 24
Case conversion functions are frequently used in WHERE clause to match specific texts. For example, if
you want to retrieve records of those departments which contain the text SALE in its name, then you may
write the following statement.
SELECT *
FROM DEPARTMENTS
WHERE UPPER(DEPARTMENT_NAME) LIKE '%SALE%' ;
SELECT *
FROM DEPARTMENTS
WHERE LOWER(DEPARTMENT_NAME) LIKE '%sale%' ;
Any of the above two statements will retrieve the required records successfully. However, if no functions
were used, then the query may not retrieve all records due to case differences. For examples, if there were
two departments named as Sales Office and Whole sale, then comparing without functions may not be
able to retrieve both records simultaneously.
Description
SUBSTR(Column, m [, n])
LENGTH (Column)
INSTR(Column, text)
LPAD(Column, n, text)
RPAD(Column, n, text)
TRIM(Column)
Function
Output
CONCAT(Hello, world)
Hello world
SUBSTR(Hello world, 7)
World
SUBSTR(Hello world, 1, 5)
Hello
LPAD(12345, 10, *)
*****12345
RPAD(12345, 10, *)
12345*****
Hello world
REPLACE(Hesso worsd, s, l)
Hello world
The following statements show the use of the above functions in SELECT query.
SELECT CONCAT(FIRST_NAME, LAST_NAME) NAME, JOB_ID
FROM EMPLOYEES
WHERE INSTR( UPPER(JOB_ID), 'CLERK') > 0 ;
SELECT ( SUBSTR(FIRST_NAME, 1, 1) || '.' || SUBSTR(LAST_NAME, 1, 1) || '.' ) ABBR
FROM EMPLOYEES ;
SELECT INITCAP( TRIM(LAST_NAME) )
FROM EMPLOYEES ;
The first query retrieves name and job id of all employees whose job id field contains the word CLERK.
The second query outputs the abbreviation of all employee names. The third query prints the last name
and padded salary in 10 character width.
Practice 3.1
a. Print the first three characters and last three characters of all country names. Print in capital
letters.
b. Print all employee full names (first name followed by a space then followed by last name).
All names should be printed in width of 60 characters and left padded with '*' symbol for
names less than 60 characters.
Page 26
2. Number functions
ROUND, TRUNC, and MOD functions
There are three number functions most commonly used in Oracle. They are given below.
Function
Description
ROUND (Column, n)
TRUNC (Column, n)
MOD(m, n)
Output
ROUND(45.923, 2)
45.92
ROUND(45.926, 2)
45.93
ROUND(45.926, 0)
46
TRUNC(45.923, 2)
45.92
TRUNC(45.926, 2)
45.92
TRUNC(45.926, 0)
45
MOD(23, 5)
Page 27
WHERE DEPARTMENT_ID = 80 ;
SELECT LAST_NAME, TRUNC(SALARY/1000, 0) || ' thousands ' ||
TRUNC( MOD(SALARY,1000)/100, 0) || ' hundreds ' || MOD(SALARY,100) || ' taka
only'
FROM EMPLOYEES ;
Practice 3.2
a. Print employee last name and number of days employed. Print the second information
rounded up to 2 decimal places.
b. Print employee last name and number of years employed. Print the second information
truncated up to 3 decimal place.
3. Date functions
Use of SYSDATE function
The SYSDATE function returns the current database server date and time. You can use this function as
follows in SELECT query.
SELECT (SYSDATE - HIRE_DATE)/7 "WEEKS EMPLOYED"
FROM EMPLOYEES
WHERE DEPARTMENT_ID = 80 ;
Note the use of double quotes around WEEKS EMPLOYED. It is necessary as the aliasing text
contains spaces. The SYSDATE is used here to find the number of days an employee has worked, and
then this number is divided by 7 to find the number of weeks, the employee passed in the company.
Date arithmetic
You can use arithmetic operators to subtract dates, add some numeric value with dates, etc. In the
previous query, you subtracted SYSDATE from HIRE_DATE, and the result is the number of days
between these two dates. The following table explains the outcomes of different arithmetic operators that
can be applied on DATE type values.
Operation
Page 28
Outcome
DATE + number
DATE number
DATE DATE
DATE + DATE
Invalid operation
Suppose the value of HIRE_DATE column for an employee is 05-FEB-1995. Then, the following table
shows the use date arithmetic operations.
Operation
Outcome
HIRE_DATE + 7
HIRE_DATE 4
SYSDATE HIRE_DATE
Outcome
MONTHS_BETWEEN(date1, date2)
ADD_MONTHS(date1, n)
ROUND(date, MONTH)
ROUND(date, YEAR)
TRUNC(date, MONTH)
TRUNC(date, YEAR)
Page 29
If we assume SYSDATE = 20-MAR-14 then the following table illustrates some outputs of the date
functions.
Expression
Outcome
ADD_MONTHS(SYSDATE, 5)
20-AUG-14
ROUND(SYSDATE, MONTH)
01-APR-14
ROUND(date, YEAR)
01-MAR-14
TRUNC(date, MONTH)
01-JAN-14
TRUNC(date, YEAR)
01-JAN-14
Practice 3.3
a. For all employees, find the number of years employed. Print first names and number of years
employed for each employee.
b. Suppose you need to find the number of days each employee worked during the first month
of his joining. Write an SQL query to find this information for all employees.
If expr1 evaluated to NULL, the NVL function outputs expr2, otherwise, output is expr1.
The following query outputs COMMISSION_PCT value for all employees. Whenever,
COMMISSION_PCT is NULL, the output shows a 0 instead of NULL.
Page 30
The NVL function can also be used in where to check if a column contains NULL value. For example, the
following statement selects all employee records, whose COMMISSION_PCT value is NULL. We
assume that, usually COMMISSION_PCT value is not negative.
SELECT *
FROM EMPLOYEES
WHERE NVL(COMMISSION_PCT, -1) = -1 ;
A better use of the NVL function is shown below where total annual salary is calculated for all
employees. Without the NVL function, the expression SALARY*12 +
SALARY*12*COMMMISSION_PCT would result in NULL whenever COMMISSION_PCT is NULL.
SELECT LAST_NAME,
(SALARY*12 + SALARY*12*NVL(COMMISSION_PCT, 0) ) ANNSAL
FROM EMPLOYEES
WHERE NVL(COMMISSION_PCT, -1) = -1 ;
Practice 3.4
a. Print the commission_pct values of all employees whose commission is at least 20%. Use
NVL function.
b. Print the total salary of an employee for 5 years and 6 months period. Print all employee last
names along with this salary information. Use NVL function assuming that salary may
contain NULL values.
Page 31
Convert a DATE value to VARCHAR2 value (in default date format). This conversion is applied
in most operations like comparison, concatenation, etc.
Convert a VARCHAR2 value to a date value provided that VARCHAR2 text is in a default date
format. Otherwise, automatic conversion fails. The default date format in Oracle is DD-MONYY or DD-MON-YYYY.
Description
MOD(25, 3)
ADD_MONTHS(31-JAN-2011, 5)
ADD_MONTHS(JAN/31/2011, 5)
CONCAT(Today is , SYSDATE)
Hello | | 123
512 + 123
512 hello
SYSDATE 01-MON-1998
Page 32
So, whenever, default conversion does not work, we need to use manual conversion functions.
The format string specifies how to convert the DATE value to VARCHAR2 value. The following table
illustrates the format texts that are most commonly applied to DATE value. Assume that, the value of
HIRE_DATE is 31-JAN-1995.
Expression
TO_CHAR(HIRE_DATE, DD/MM/YYYY)
31/01/1995
YEAR)
TO_CHAR(123456)
123456
The last example in above table shows that, TO_CHAR function can applied to numeric values also.
Page 33
However, the above query may not give correct ordering because POSTAL_CODE column is of type
VARCHAR2. So, Oracle will do the ordering lexicographically (1000 will come before 999). To do
numerical order, you can use the following query instead.
SELECT STREET_ADDRESS, POSTAL_CODE
FROM LOCATIONS
ORDER BY TO_NUMBER(POSTAL_CODE) ASC ;
The following table illustrates the use of TO_DATE function with examples.
Expression
Works fine.
TO_DATE(31/12/1995, DD/MM/YYYY)
Works fine.
TO_DATE(1995-12-31, YYY-MM-DD)
Works fine.
TO_DATE(1995-12-31, YYY-DD-MM)
You are always encouraged to use explicit date conversions in comparison operations. Otherwise, you
query may bring unexpected results. For example, the following query finds all employee last names who
was hired before 1st January 1997.
SELECT LAST_NAME, TO_CHAR(HIRE_DATE, 'DD-MON-YYYY') HD
FROM EMPLOYEES
WHERE HIRE_DATE < TO_DATE('01-JAN-1997', 'DD-MON-YYYY')
ORDER BY HIRE_DATE ASC ;
Page 34
Practice 3.5
a. Print hire dates of all employees in the following formats:
(i) 13th February, 1998 (ii) 13 February, 1998.
Page 35
Description
SUM (Column)
Finds the total, i.e., summation of values in Column for all rows
in the group
MAX(Column)
Finds the maximum value in Column for all rows in the group
MIN(Column)
Finds the minimum value in Column for all rows in the group
AVG(Column)
Finds the average value in Column for all rows in the group
COUNT(Column)
The group functions given above discard NULL values during their computation.
Page 36
In the above statement, Oracle will first create several groups based on <Column1, Column2,>. Every
unique combination of these columns will denote a group and all rows in the table that have these
combinations of values will be in the group. Note that, only the columns in the GROUP BY clause can be
selected along with group function expressions.
For example, suppose, you want to create a report showing the total salary paid by the company to each
departments. This requires a GROUP BY query and group function as shown below.
SELECT DEPARTMENT_ID, SUM(SALARY)
FROM EMPLOYEES
GROUP BY DEPARTMENT_ID ;
For another example, suppose, you want to know the maximum salary, minimum salary and average
salary the company pays in different job types. The following GROUP BY query will retrieve the
required information.
SELECT JOB_ID, MAX(SALARY), MIN(SALARY), AVG(SALARY)
FROM EMPLOYEES
GROUP BY JOB_ID ;
Note that, you cannot select a column that is not present in GROUP BY clause. For example, the
following query would return an error.
SELECT JOB_ID, JOB_TITLE, COUNT(*) TOTAL
FROM JOBS
GROUP BY JOB_ID ;
For the third example, suppose you want to know the number of employees working in each department.
As you may recall, this requires creating a group based on DEPARTMENT_ID column, then count the
number of rows in each group, and then output the information. So, you may think, the following query
will output the information.
SELECT DEPARTMENT_ID, COUNT(LAST_NAME)
FROM EMPLOYEES
GROUP BY DEPARTMENT_ID ;
Page 37
In the above statement, counting the LAST_NAME column is similar to counting any other columns.
However, COUNT(LAST_NAME) will ignore the NULL values in LAST_NAME field, therefore not
counting rows that contain NULL values in LAST_NAME field. The correct query should be the
following.
SELECT DEPARTMENT_ID, COUNT(*)
FROM EMPLOYEES
GROUP BY DEPARTMENT_ID ;
In the above, COUNT(*) counts number of rows (NULL and non-NULL) and therefore will give the
correct result.
Page 38
The following statement finds the maximum and minimum salary for each job types for only the
employees working in the department no. 80.
SELECT JOB_ID, MAX(SALARY), MIN(SALARY)
FROM EMPLOYEES
WHERE DEPARTMENT_ID = 80
GROUP BY JOB_ID ;
Practice 4.1
a. For all managers, find the number of employees he/she manages. Print the MANAGER_ID
and total number of such employees.
b. For all departments, find the number of employees who get more than 30k salary. Print the
DEPARTMENT_ID and total number of such employees.
c. Find the minimum, maximum, and average salary of all departments except
DEPARTMENT_ID 80. Print DEPARTMENT_ID, minimum, maximum, and average salary.
Sort the results in descending order of average salary first, then maximum salary, then
minimum salary. Use column alias to rename column names in output for better display.
Page 39
Note that, the use of DISTINCT does not change the result of MAX and MIN group function But, it does
change the outcomes of SUM, and COUNT functions.
Note that, the HAVING condition is applied after group information is calculated unlike WHERE
condition is applied before grouping.
The following statements show some more examples of HAVING clause.
Page 40
The first statement above outputs maximum and minimum salary for each job types. However, only those
results are printed where group maximum is greater than 5000. The second query retrieves average salary
of each job type. This time, only those group results are printed for which average salary is less than or
equal to 5000. Results are sorted in descending order of average salary.
Practice 4.2
a. Find for each department, the average salary of the department. Print only those
DEPARTMENT_ID and average salary whose average salary is at most 50k.
The following query finds the total number of employees whose name starts with the same character. The
query reports the first character and total employees.
Page 41
An important reason for adding more than one column in a GROUP BY clause is to select more columns.
Consider the following query that finds the number of employees for each job type.
SELECT JOB_ID, COUNT(*) TOTAL
FROM JOBS
GROUP BY JOB_ID ;
Now, if we want to print job titles along with job id in the above query, we has to put the job title column
in the GROUP BY clause, because Oracle does not allow to select columns in the SELECT clause that are
not present in the GROUP BY clause.
SELECT JOB_ID, JOB_TITLE, COUNT(*) TOTAL
FROM JOBS
GROUP BY JOB_ID, JOB_TITLE ;
Practice 4.3
a. Find number of employees in each salary group. Salary groups are considered as follows.
Group 1: 0k to <5K, 5k to <10k, 10k to <15k, and so on.
Page 42
b. Find the number of employees that were hired in each year in each job type. Print year, job id,
and total employees hired.
Page 43
The following example statement joins EMPLOYEES and DEPARTENT tables based on the values of
DEPARTMENT_ID column. A row from EMPLOYEES table is joined with a row from
DEPARTMENTS table where both rows have the same DEPARTMENT_ID value.
SELECT E.LAST_NAME, D.DEPARTMENT_NAME
FROM EMPLOYEES E JOIN DEPARTMENTS D USING (DEPARTMENT_ID) ;
Page 44
Note the use of table aliases in the above statement. The table aliases are used in SELECT clause to
choose columns from the tables. However, you cannot alias the column, i.e., DEPARTMENT_ID which
is used in the USING clause. Otherwise, Oracle will generate error message. The following query clarifies
this by not aliasing the DEPARTMENT_ID column in the SELECT clause.
SELECT E.LAST_NAME, DEPARTMENT_ID, D.DEPARTMENT_NAME
FROM EMPLOYEES E JOIN DEPARTMENTS D USING (DEPARTMENT_ID) ;
E.DEPARTMENT_ID,
D.DEPARTMENT_NAME
The more general nature of the ON clause will be clear if you observer the following statements.
Page 45
Self-join allows many interesting queries. Suppose you want to create a report showing last name of an
employee and a number which is the number of employees getting higher salary than the employee. This
type of results can be calculated using joins and groupings. The following statement computes this.
SELECT E1.LAST_NAME, COUNT(*) HIGHSAL
FROM EMPLOYEES E1 JOIN EMPLOYEES E2
ON (E1.SALARY < E2.SALARY)
GROUP BY E1.EMPLOYEE_ID, E1.LAST_NAME
ORDER BY E1.LAST_NAME ASC ;
Observe that in the above query, the E1.LAST_NAME column was not required to be put in the GROUP
BY clause unless it was selected in SELECT clause.
Page 46
If you replace COUNT(E2.EMPLOYEE_ID) by COUNT(*) in the above query, then the query would not
output correct results! Find the reason yourself! Morever, E1.LAST_NAME does not any effect on
grouping. It was included in the grouping clause so that it can be selected in the output.
Practice 5.1
a. For each employee print last name, salary, and job title.
b. For each department, print department name and country name it is situated in.
c. For each country, finds total number of departments situated in the country.
d. For each employee, finds the number of job switches of the employee.
e. For each department and job types, find the total number of employees working. Print
department names, job titles, and total employees working.
Page 47
f.
For each employee, finds the total number of employees those were hired before him/her.
Print employee last name and total employees.
g. For each employee, finds the total number of employees those were hired before him/her and
those were hired after him/her. Print employee last name, total employees hired before him,
and total employees hired after him.
h. Find the employees having salaries greater than at least three other employees
i.
For each employee, find his rank, i.e., position with respect to salary. The highest salaried
employee should get rank 1 and lowest salaried employee should get the last rank. Employees
with same salary should get same rank value. Print employee last names and his/he rank.
j.
Finds the names of employees and their salaries for the top three highest salaried employees.
The number of employees in your output should be more than three if there are employees
with same salary.
Page 48
The sub-query executes before the main query and results of sub-query are used in main query.
Sub-query can result in one row or multiple rows. In the above statement, sub-query is first executed, and
SALARY value of Abel is retrieved. Then, this value is used in the main query.
Page 49
The following is another example where the main query retrieves information of those employees whose
JOB_ID is same as the employee numbered 141.
SELECT LAST_NAME, SALARY
FROM EMPLOYEES
WHERE JOB_ID =
(
SELECT JOB_ID
FROM EMPLOYEES
WHERE EMPLOYEE_ID = 141
) ;
Page 50
SALARY =
(
SELECT MAX(SALARY)
FROM EMPLOYEES
)
ANY If used with comparison operation, the outcome will be true if operator evaluates to true
for any of the sub-query values
ALL if used with comparison operator, the outcome will be true only if operator evaluates to
true for all values returned by the sub-query
To understand the use of ANY and ALL, examine the following statement. The query retrieves those
employee records (working in other than IT_PROG department) whose SALARY is less than at least
one employee of IT_PROG.
SELECT LAST_NAME, JOB_ID, SALARY
FROM EMPLOYEES
WHERE
In the query below, ALL is used instead of ANY. This query retrieves those employee records whose
SALARY is less than all employees of IT_PROG.
SELECT LAST_NAME, JOB_ID, SALARY
FROM EMPLOYEES
WHERE
Page 51
Practice 6.1
a. Find the last names of all employees that work in the SALES department.
b. Find the last names and salaries of those employees who get higher salary than at least one
employee of SALES department.
c. Find the last names and salaries of those employees whose salary is higher than all employees
of SALES department.
d. Find the last names and salaries of those employees whose salary is within 5k of the
average salary of SALES department.
2. Advanced Sub-query
Correlated Sub-query
In a correlated sub-query, we use row references of the main query to in the sub-query. Suppose, you
need to retrieve those employees whose salary is higher than at least three other employees. To write this
query using sub-query, we need to do the following:
SELECT *
FROM EMPLOYEES E1
WHERE 3 <= (
SELECT COUNT(*)
FROM EMPLOYEES E2
WHERE E2.SALARY < E1.SALARY
)
In the above query, the sub-query in the WHERE clause retrieve those rows form EMPLOYEES table
who earn less salary than the salary of the current employee. The current is determined by the execution
Page 52
of this query by Oracle. Oracle retrieves all records of the main query first. Then for each row (say ) of
this main query (outer query), Oracle executes the sub-query by setting E1.SAL value to the salary value
of row . Then sub-query results are retrieved, conditions are evaluated, and then X goes to final output if
condition becomes true. If main query returns
times.
EXISTS
(
SELECT *
FROM EMPLOYEES E
WHERE E.DEPARTMENT_ID = D.DEPARTMENT_ID AND JOB_ID = 'IT_PROG'
) ;
The following query uses NOT EXISTS to find those employees whose earns the maximum salary in
his/her department.
SELECT LAST_NAME, SALARY, DEPARTMENT_ID
FROM EMPLOYEES E1
WHERE
NOT EXISTS
(
SELECT *
FROM EMPLOYEES E2
WHERE E2.DEPARTMENT_ID = E1.DEPARTMENT_ID AND
E2.SALARY > E1.SALARY
)
Page 53
NOT EXISTS
(
SELECT *
FROM EMPLOYEES E2
WHERE E2.DEPARTMENT_ID = E1.DEPARTMENT_ID AND
E2.SALARY > E1.SALARY
)
The above query can be solve by placing a sub-query in the FROM clause as shown below.
SELECT E.LAST_NAME, E.SALARY, D.MINSAL, D.MAXSAL
FROM EMPLOYEES E,
Page 54
(
SELECT DEPARTMENT_ID AS DEPT, MIN(SALARY) MINSAL, MAX(SALARY) MAXSAL
FROM EMPLOYEES
GROUP BY DEPARTMENT_ID
) D
WHERE (E.DEPARTMENT_ID = D.DEPT)
ORDER BY E.SALARY ;
The sub-query in the FROM clause above creates temporary table whose schema is D(DEPT, MINSAL,
MAXSAL). Then Oracle joins E with D and rest of the query executes as usual.
Practice 6.2
a. Find those employees whose salary is higher than at least three other employees. Print last
names and salary of each employee. You cannot use join in the main query. Use sub-query in
WHERE clause only. You can use join in the sub-queries.
b. Find those departments whose average salary is greater than the minimum salary of all other
departments. Print department names. Use sub-query. You can use join in the sub-queries.
c. Find those department names which have the highest number of employees in service. Print
department names. Use sub-query. You can use join in the sub-queries.
d. Find those employees who worked in more than one department in the company. Print
employee last names. You cannot use join in the main query. Use sub-query. You can use join
in the sub-queries.
e. For each employee, find the minimum and maximum salary of his/her department. Print
employee last name, minimum salary, and maximum salary. Do not use sub-query in
WHERE clause. Use sub-query in FROM clause.
f.
For each job type, find the employee who gets the highest salary. Print job title and last name
of the employee. Assume that there is one and only one such employee for every job type.
Page 55
SET-OPERATOR
(
SELECT Column1, Column2, , ColumnN
FROM table_name
The data type of each column in the second query must match the data type of its corresponding
column in the first query.
Set operator
Description
UNION
UNION ALL
INTERSECT
MINUS
Page 56
The UNION ALL operator combines results of two queries and keeps duplicate values.
SELECT EMPLOYEE_ID, JOB_ID
FROM EMPLOYEES
UNION ALL
(
SELECT EMPLOYEE_ID, JOB_ID
FROM JOB_HISTORY
) ;
INTERSECT operator
The intersect operator performs the set intersection. Rows that are common in both queries are retrieved
in the output. The following statement finds the employees whose current job title is same as one of their
previous job titles.
SELECT EMPLOYEE_ID, JOB_ID
FROM EMPLOYEES
INTERSECT
(
SELECT EMPLOYEE_ID, JOB_ID
FROM JOB_HISTORY
) ;
Page 57
MINUS operator
The MINUS operator performs set minus operation. Rows of first query that are not in the second query
will be retrieved for output. The following query finds the employees who have not changed their jobs
even once.
SELECT EMPLOYEE_ID, JOB_ID
FROM EMPLOYEES
MINUS
(
SELECT EMPLOYEE_ID, JOB_ID
FROM JOB_HISTORY
) ;
But, the above statement would generate an error message as the JOB_ID fields of the two tables have
different data types. So, in order to match the data types explicitly, you will require converting the data
type of the second query to VARCHAR2 as follows.
SELECT LAST_NAME, JOB_ID, SALARY
FROM EMPLOYEES
UNION ALL
Page 58
(
SELECT LAST_NAME, TO_CHAR(JOB_ID), SALARY
FROM EMPLOYEES2
) ;
Practice 7.1
a. Find EMPLOYEE_ID of those employees who are not managers. Use minus operator to
perform this.
b. Find last names of those employees who are not managers. Use minus operator to perform
this.
c. Find the LOCATION_ID of those locations having no departments.
Page 59
For example, the following statement inserts a new row in the DEPARTMENTS table.
INSERT INTO DEPARTMENTS (DEPARTMENT_ID, DEPARTMENT_NAME, MANAGER_ID, LOCATION_ID)
VALUES (179, 'Public Relations', 100, 2600) ;
Values are given in the default order of the columns as defined in the table creation statements.
For example, the following statement would successfully insert a row in the DEPARTMENTS table.
INSERT INTO DEPARTMENTS VALUES (189, 'PRINTING_STATIONARY', 100, 2600) ;
Page 60
However, the following insert statement would not work and will generate an Oracle error message. The
reason is that, the DEPARTMENTS table has four columns, but in the statement only values are specified
for two columns only.
INSERT INTO DEPARTMENTS VALUES (170, 'Public Relations') ;
The following insert statement will also fail. Even though, all values are specified, they are not in correct
order as defined in the original table definition.
INSERT INTO DEPARTMENTS VALUES (170, 100, 'Public Relations', 1700) ;
In the above INSERT statement, rows will successfully be inserted. Since, values for MANAGER_ID and
LOCATION_ID columns were not specified; they will be filled with NULL. Note that, this will work
only if these columns satisfy the following conditions:
Page 61
However, if you specify the text in default date format, i.e, DD-MON-YYYY, then TO_DATE function
is not required as shown in the following statement. Oracle will automatically convert the text to DATE
type value. However, it is a good practice to always use the TO_DATE function to explicitly convert
to DATE values.
INSERT INTO EMPLOYEES VALUES (279, 'Den', 'Raphealy', 'Drapheal', '515.127.4515',
'13-FEB-1999', 'SA_REP', 11000, 0.2, 100, 60) ;
You can also use sub-query and where condition to copy some specific rows as shown in the following
statement.
INSERT INTO SALES_EMPLOYEES (ID, NAME, SALARY, COMMISSION_PCT)
SELECT EMPLOYEE_ID, LAST_NAME, SALARY, COMMISSION_PCT
FROM EMPLOYEES
WHERE JOB_ID LIKE '%REP%' ;
Page 62
To change the DEPARTMENT_ID of all employees, i.e., all rows in the table, omit the WHERE clause
as shown below:
UPDATE EMPLOYEES
SET DEPARTMENT_ID = 110 ;
Page 63
Practice 8.2
a. Update COMMISSION_PCT value to 0 for those employees who have NULL in that
column.
b. Update salary of all employees to the maximum salary of the department in which he/she
works.
c. Update COMMISSION_PCT to
employees he/she manages. When
is the number of
column.
d. Update the hiring dates of all employees to the first day of the same year. Do not change this
for those employees who joined on or after year 2000.
The following statement removes the Finance department row from the DEPARTMENTS table. Actually,
it will not remove any row due to violation of constraints!
DELETE FROM DEPARTMENTS
WHERE DEPARTMENT_NAME = 'Finance' ;
Page 64
The following statement removes two rows from the DEPARTMENT table. Actually, it will not remove
any row due to violation of constraints!
DELETE FROM DEPARTMENTS
WHERE DEPARTMENT_ID IN (30, 40) ;
Note that, the following statement will remove all rows from the DEPARTMENTS table as there is no
WHERE condition. Actually, it will not remove any row due to violation of constraints!
DELETE FROM DEPARTMENTS ;
Note that use of UPPER function in the above query. The UPPER function ensures that, the statement
will work even in department names are stored in lower case or upper case letters.
Practice 8.3
a. Delete those employees who earn less than 5k.
b. Delete those locations having no departments.
c. Delete those employees from the EMPLOYEES table who joined before the year 1997.
Page 65
The user exits SQL*DEVELOPER or SQL*PLUS (automatic COMMIT)! Do not forget this in
your entire life!
After one transaction ends, another transaction will start with the execution of next DML statement.
COMMIT statement
The COMMIT statement saves results of DML operations of the current transaction permanently in
database. It also ends the ongoing transaction.
The following statements show the use of COMMIT to store data permanently to database. One row is
deleted from the EMPLOYEES table and a row is added to the DEPARTMENTS table. Finally,
COMMIT saves this changed permanently into database.
DELTE FROM EMPLOYEES
WHERE EMPLOYEE_ID = 99999 ;
INSERT INTO DEPARTMENTS
VALUES (290, Corporate Tax, NULL, 1700) ;
COMMIT ;
Page 66
ROLLBACK Statement
The ROLLBACK statement undoes the results of all DML operations executed in the current transaction.
It also ends the current transaction. The state of the tables will be restored in the previous values before
the current transaction started.
The following statements when executed will not store the new row in the DEPARTMENTS table and
will not remove the row from the EMPLOYEES table. The ROLLBACK statement will undo all the
changes done by the DELETE and INSERT statements.
DELTE FROM EMPLOYEES
WHERE EMPLOYEE_ID = 99999 ;
INSERT INTO DEPARTMENTS
VALUES (290, Corporate Tax, NULL, 1700) ;
ROLLBACK ;
5. Practice Problems
In class.
Page 67
Specifying constraints in tables NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY,
CHECK
1. Creating Tables
CEATE TABLE statement
The CREATE TABLE statement is used to create new tables in database. The general syntax of the
statement is given below:
CREATE TABLE [schema_name.]table_name
(
Column1 Datatype1,
Column2 Datatype2,
) ;
For example, the following example creates a new table in the database:
CREATE TABLE PERSON
(
NID VARCHAR2(15),
NAME VARCHAR2(50),
BDATE DATE
) ;
The above statement will create a table named PERSON in database. The table PERSON will have three
columns which are:
Page 68
Naming rules
Table names and column names have to satisfy the following
Must not duplicate the name of another object of the same user
The PERSON table created above will have a default value, i.e., SYSDATE for the BDATE column. So,
if user does not specify any value for this parameter, then the default value will be used for the column.
For example, the following INSERT statement does not specify value for the BDATE column. The value
of SYSDATE will be used by default for the BDATE column.
INSERT INTO PERSON(NID, NAME) VALUES ('10010010010001', 'Sakib') ;
Page 69
Description
VARCHAR2(size) Used to store variable length text data. A maximum size must be
specified. The minimum size is 1 and maximum size is 4000.
CHAR(size)
Used to store fixed length text data. Minimum size is 1 and maximum
size is 2000.
NUMBER(p, s)
DATE
CLOB
BLOB
For example, the following statement creates a table DEPT80 with a sub-query.
CREATE TABLE DEPT80
AS
SELECT EMPLOYEE_ID, LAST_NAME, SALARY*12 ANNSAL
FROM EMPLOYEES
WHERE DEPARTMENT_ID = 80 ;
Page 70
The data types of the three columns are inherited from the EMPLOYEES table. So, the data types
of the three columns reflect the same as in the EMPLOYEES table.
The newly created table will inherit all constraints that are defined on the EMPLOYEE_ID,
LAST_NAME columns in the EMPLOYEE table.
The newly created table will contain all data rows of employees whose DEPARTMENT_ID
column value is 80.
Note that, the column alias ANNSAL for the expression SALARY*12 is necessary here.
Otherwise, Oracle will generate an error message.
Enforce rules on the data. Whenever, a row is inserted, updated, or deleted, these rules are
checked against the data. Constraints must be satisfied for the operation to be successful.
Constraints prevent the deletion of important rows from a table, which may have dependencies in
other tables
Description
NOT NULL
UNIQUE
PRIMARY KEY
FOREGIN KEY
Page 71
Defining constraints
Constraints can be defined in column-level and table-level. The general syntax of column-level constraint
definition is as follows:
CREATE TABLE [schema_name.]table_name
(
,
Column datatype [CONSTRAINT constraint_name] constraint_type,
) ;
) ;
Page 72
NID column is the PRIMARY KEY of the table. So, NID will uniquely specify each row of the
table. Moreover, NID cannot be NULL for any row inserted in the table.
The PRIMARY KEY constraint of NID column has been given a name, i.e., PERSON_PK
NAME column cannot have NULL values. This constraint is not given any name.
The following statement creates the same constraints, but this time, constraints are defined in table-level
with no difference.
DROP TABLE PERSON;
CREATE TABLE PERSON
(
NID VARCHAR2(15),
NAME VARCHAR2(50) NOT NULL UNIQUE,
BDATE DATE DEFAULT SYSDATE,
CONSTRAINT PERSON_PK PRIMARY KEY (NID)
) ;
In some cases, two columns together may uniquely identify each row of a table. So, PRIMARY KEY is
composed of two column values rather than a single column. This type of constraints cannot be defined
using column-level constraints. They must be defined using table-level constraints as shown below:
DROP TABLE PERSON;
CREATE TABLE PERSON
(
COUNTRYID CHAR(3),
PERSONID VARCHAR2(15),
NAME VARCHAR2(50) NOT NULL UNIQUE,
BDATE DATE DEFAULT SYSDATE,
CONSTRAINT PERSON_PK PRIMARY KEY (COUNTRYID, PERSONID)
) ;
In the above PERSON table, the PRIMARY KEY is composed of two columns, COUNTRYID, and
PERSONID.
Page 73
Now, consider the following ADDRESS table, which stores the address of each person. This person must
be a valid row of the PERSON table.
CREATE TABLE PERSON_ADDRESS
(
PID VARCHAR2(15) CONSTRAINT PERSON_ADDRESS_PK PRIMARY KEY,
ADDR_LINE1 VARCHAR2(50) NOT NULL,
ADDR_LINE2 VARCHAR2(50),
CITY VARCHAR2(50) NOT NULL,
DISTRICT VARCHAR2(50) NOT NULL,
CONSTRAINT PERSON_ADDRESS_FK FOREIGN KEY(PID) REFERENCES PERSON(NID)
)
The PID column in the PERSON_ADDRESS table is defined as the PRIMARY KEY of the table.
Moreover, this column is also specified as a FOREIGN KEY constraint which is linked (by
REFERENCES Keyword) to NID column of PERSON table. This link will ensure that if a value is
inserted in the PID column of PERSON_ADDRESS table, the same value must also be present in the
NID column of a row in the PERSON table. Otherwise, the insertion will fail. The PERSON table will be
called parent table and PERSON_ADDRESS table will be called a child table.
The FOREIGN KEY constraints create a problem during deletion of rows from the parent table. If a row
is to be deleted from the parent table, but the child table have some rows which are dependent (because of
Page 74
the FOREIGN KEY constraint) on that row, then Oracle will not allow deletion of the row. All dependent
rows in the child table must be deleted manually before the deletion of a row in the parent table.
However, there are two solutions available in Oracle. The FOREIGN KEY constraints can have following
optional keywords at the end of the constraint definition
ON DELETE CASCADE When a row is deleted from the parent table, the dependent rows are
also deleted from the child table automatically by Oracle.
ON DELETE SET NULL When a row is deleted from the parent table, the dependent rows are
set to NULL values in the child table automatically by Oracle.
CHECK constraints
The CHECK constraints define one or more conditions that must be satisfied by the column values of a
row. These constraints can be defined as column-level or table-level. The general syntax of the CHECK
constraint is given below:
CHECK ( condition )
For example, the following table definition contains a CHECK constraint in column-level which ensure
that, the SALARY value cannot be negative.
DROP TABLE EMPLOYEE2;
CREATE TABLE EMPLOYEE2
(
EID VARCHAR2(15) CONSTRAINT EMPLOYEE2_PK PRIMARY KEY,
SALARY NUMBER CONSTRAINT EMPLOYEE_SAL_MIN CHECK (SALARY > 0)
) ;
Is defined in column-level
Page 75
For example, the following statement removes the EMPLOYEES2 table from the database.
DROP TABLE EMPLOYEES2 ;
Note that, the table structure is deleted and all rows are deleted. But, the space used by the table is not
released. To release the storage used by the table, you need to specify PURGE option at the end of the
DROP TABLE statements as shown below:
DROP TABLE EMPLOYEES2 PURGE ;
To delete a column from a table, use the ALTER TABLE DROP command like below.
ALTER TABLE EMPLOYEES DROP COLUMN BDATE ;
Page 76
Views stores sub set of data from tables, created with CREATE VIEW statement.
1. Creating Views
What is a View
A view
Contains no data of its own, and contain no data at the physical level.
When user executes query on the view, the view sub-query gets executed and view data are
fetched dynamically
Page 77
The view does not contain any physical records at the time of creation.
The sub-query is not executed. It will be executed later when view data are required by another
query on the view.
OR REPLACE clause is optional and if it is specified, then the view is created even though a
view with the same name already exists. The old view is deleted.
The column alias ANNSAL is necessary here, otherwise Oracle will generate an error message.
You can issue SQL SELECT statements on the created view to retrieve data as follows:
SELECT * FROM DEPTV80 ;
SELECT EMPLOYEE_ID, ANNSAL FROM DEPTV80 ;
JOIN DEPARTMENTS D
ON (E.DEPARTMENT_ID = D.DEPARTMENT_ID)
GROUP BY D.DEPARTMENT_ID, D.DEPARTMENT_NAME ;
The column aliases in the sub-query are necessary; otherwise Oracle will generate error
messages.
Since, the view sub-query contains JOIN and GROUP BY clause, DEPT_SUMMARY will be a
complex view. In complex view, no DML operations are allowed unlike the simple views where
DML operations are allowed.
Page 78
Views give different view of the same table to different users of the database.
Views do not contain any record of its own which saves a lot of space of the database than
copying a table multiple times.
2. Creating Sequences
What is a Sequence
A sequence is a database objects that create numeric (integer) values. The sequence is usually used to
create values for a table column, e.g., PID column in the PERSON table defined in previous chapters.
Remember the PERSON table created in previous chapter with the following statement.
Page 79
Now, the following statement creates a sequence named PERSON_NID_SEQ to be used for inserting
rows in PERSON table.
CREATE SEQUENCE PERSON_NID_SEQ
INCREMENT BY 1
START WITH 100000000000001
MAXVALUE 999999999999999
NOCYCLE ;
The NOCYLE option ensures that after the maximum value is generated, the sequence will stop
generating value. If you want the sequence to generate values again from the starting value, use
the CYCLE option instead of NOCYCLE option.
Page 80
You can view the current value of the sequence by the following query:
SELECT PERSON_NID_SEQ.CURRVAL
FROM DUAL ;
3. Creating Indexes
What is an Index
An index
Provides fast access to the table data using the column on which index is defined
Are automatically managed by the Oracle server after user creates the index.
For example, the following statement creates an index on the NAME column of the PERSON table
defined above. This will enable faster access of data based on NAME column. That means, if the NAME
column is used in WHERE clause of a query, then Oracle can retrieve query results more quickly than if
no index was present.
CREATE INDEX PERSON_NAME_IDX
ON PERSON (NAME) ;
You can drop an index using DROP INDEX statement as shown below:
Page 81
The table is large and most queries are expected to retrieve only less than 2% to 4% rows.
Page 82
Executable (after BEGIN) Contains SELECT statements to retrieve data from tables and
contain PL/SQL statements to manipulate those data. This is a mandatory section.
Exception (after EXCEPTION) This is an optional section. Contains exception handling codes.
The following statement shows an anonymous block that outputs Hello world.
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World') ;
END ;
/
Page 83
Note that use INTO keyword to store value from SELECT statement into PL/SQL variable (ENAME).
Page 84
MONTHS
RMONTHS
:=
:=
MONTHS_BETWEEN(SYSDATE, JDATE) ;
ROUND(MONTHS, 0) ;
Note that, the assignment operator in PL/SQL is colon-equal (). The equal (=) operator is the equality
comparison operator and cannot be used as an assignment operator. Do not give space between the colon
(:) and equal (=) of the colon-equal () operator, otherwise it will generate an error.
Oracle will not compile the erroneous blocks. You must correct the errors and re-run the corrected code.
The following example shows the use of IF-ELSE in PL/SQL. The script finds whether employee
numbered 100 worked for more than 10 years in the company.
DECLARE
JDATE DATE ;
Page 85
YEARS NUMBER ;
BEGIN
SELECT HIRE_DATE INTO JDATE
FROM EMPLOYEES
WHERE EMPLOYEE_ID = 100 ;
YEARS :=
The following example shows another use of IF-ELSE statement to find the grade level of employee
numbered 100.
DECLARE
ESALARY NUMBER ;
BEGIN
SELECT SALARY INTO ESALARY
FROM EMPLOYEES
WHERE EMPLOYEE_ID = 100 ;
IF ESALARY < 1000 THEN
DBMS_OUTPUT.PUT_LINE('Job grade is D') ;
ELSIF ESALARY >= 1000 AND ESALARY < 2000 THEN
DBMS_OUTPUT.PUT_LINE('Job grade is C') ;
ELSIF ESALARY >= 2000 AND ESALARY < 3000 THEN
DBMS_OUTPUT.PUT_LINE('Job grade is B') ;
ELSIF ESALARY >= 3000 AND ESALARY < 5000 THEN
DBMS_OUTPUT.PUT_LINE('Job grade is A') ;
ELSE
DBMS_OUTPUT.PUT_LINE('Job grade is A+') ;
END IF ;
END ;
/
Do not forget to use THEN after each ELSIF clause. This is a common mistake everyone does.
Page 86
Page 87
In our example above, we used two pre-defined exception names: NO_DATA_FOUND and
OTHERS. There are many pre-defined exception names in Oracle. You must have the knowledge
Page 88
of these exception names as Oracle throws such exceptions for several types of errors while
processing a statement.
NO_DATA_FOUND
TOO_MANY_ROWS
DUP_VAL_ON_INDEX
NVALID_NUMBER
VALUE_ERROR
ZERO_DIVIDE
Practice 11.2
a. Extend the above block by handing the following exception: TOO_MANY_ROWS. Print an
appropriate message when such an exception occurs.
b. Write an example PL/SQL block that inserts a new arbitrary row to the COUNTRIES table.
The block should handle the exception DUP_VAL_ON_INDEX and OTHERS. Run the
block for different COUNTRY_ID and observe the cases when above exception occurs.
Page 89
Statement2 ;
END LOOP ;
END LOOP ;
The following example prints the numbers from 1 to 100 using WHILE loop.
DECLARE
i number;
BEGIN
i := 1;
WHILE i<=100
LOOP
DBMS_OUTPUT.PUT_LINE(i);
i := i + 1;
END LOOP ;
End ;
/
Page 90
There is a type of loop called unconditional-loop in Oracle PL/SQL. The following example shows how
to write the unconditional loop to print the numbers from 1 to 100.
DECLARE
i number;
BEGIN
--this is an unconditional loop, must have EXIT WHEN inside loop
i := 1;
LOOP
DBMS_OUTPUT.PUT_LINE(i);
i := i + 1;
EXIT WHEN
(i > 100) ;
END LOOP ;
End ;
/
Note the statement EXIT WHEN to exit the unconditional loop. This is a must in an unconditional loop
otherwise the loop will run for-over. Also note that EXIT WHEN statement can also be used inside a
WHILE loop or FOR loop to exit at any time.
END LOOP ;
The following example augments our previous code of finding employees working for more than 10
years. This time, the script counts the number of employees who worked 10 years or more in the
company. Then, it displays the count.
DECLARE
Page 91
YEARS NUMBER ;
COUNTER NUMBER ;
BEGIN
COUNTER := 0 ;
--the following for loop will iterate over all rows of the SELECT results
FOR R IN (SELECT HIRE_DATE FROM EMPLOYEES )
LOOP
--variable R is used to retrieve columns
YEARS := (MONTHS_BETWEEN(SYSDATE, R.HIRE_DATE) / 12) ;
IF YEARS >= 10 THEN
COUNTER := COUNTER + 1 ;
END IF ;
END
LOOP ;
In the above script, a special variable R is used which is called a cursor-variable. Details of cursor are out
of scope of this book. In summary
The FOR LOOP ends automatically after the last row have been fetched by the cursor variable R
Only those columns are available that are retrieved in the SELECT statement (R.LAST_NAME is
invalid as LAST_NAME is not retrieved in SELECT)
Page 92
COUNTER := 0 ;
FOR R IN (SELECT EMPLOYEE_ID, SALARY, HIRE_DATE FROM EMPLOYEES )
LOOP
OLD_SAL := R.SALARY ;
YEARS := (MONTHS_BETWEEN(SYSDATE, R.HIRE_DATE) / 12) ;
IF YEARS >= 10 THEN
UPDATE EMPLOYEES SET SALARY = SALARY * 1.15
WHERE EMPLOYEE_ID = R.EMPLOYEE_ID ;
END IF ;
SELECT SALARY INTO NEW_SAL FROM EMPLOYEES
WHERE EMPLOYEE_ID = R.EMPLOYEE_ID ;
DBMS_OUTPUT.PUT_LINE('Employee id:' || R.EMPLOYEE_ID || ' Salary: '
|| OLD_SAL || ' -> ' || NEW_SAL) ;
END
LOOP ;
COMMIT;
END ;
/
Practice 11.1
a. Write a PL/SQL block that will print Happy Anniversary X for each employee X whose
hiring date is today. Use cursor FOR loop for the task.
4. PL/SQL Procedures
PL/SQL procedures and functions (to be discussed in later section) are like PL/SQL blocks except the
following:
Unlike PL/SQL (anonymous) blocks, a PL/SQL procedure or function has a name and zero or
more parameters. The parameters are used to give inputs to the procedure or function. The
function can even return values.
A PL/SQL (anonymous) block is to be saved in a separate file by the user, if he wishes to run it
later. However, a PL/SQL procedure or function can be saved in the database, so it need not be
saved in a separate file by the user.
When a procedure or function code is run in the SQL command line, the procedure or function
codes are not executed. The codes are just stored in the database. To execute the procedure, we
Page 93
will need to call it from the command line using EXEC PROC_NAME statement. To execute the
function, we need to call it in a select statement or from inside a PL/SQL block.
Wring a procedure
The general syntax of writing a PL/SQL procedure is given below.
CREATE OR REPLACE PROCEDURE <PROC_NAME> ( <PARAM1> [IN/OUT] <DATATYPE1>, ...) IS
Declaration1 ;
Declaration2 ;
... ;
BEGIN
Statement1 ;
Statement2 ;
... ;
END ;
/
Parameters can be of two types: IN and OUT. IN parameters receive input and OUT parameters
generate output (like returning values from procedure).
Let us re-write our PL/SQL block to find whether employee numbered 100 has worked10 years or more.
Let us call this procedure IS_SENIOR_EMPLOYEE. The following code shows the procedure.
CREATE OR REPLACE PROCEDURE IS_SENIOR_EMPLOYEE IS
JDATE DATE ;
YEARS NUMBER ;
BEGIN
SELECT HIRE_DATE INTO JDATE
FROM EMPLOYEES
WHERE EMPLOYEE_ID = 100 ;
YEARS :=
Page 94
END IF ;
END ;
/
If you run the above code, then the procedure is saved in the database. Later you can execute the
procedure form the SQL*PLUS command line as follows.
EXEC
IS_SENIOR_EMPLOYEE ;
You can also execute the procedure inside a PL/SQL block, inside another procedure or function as
shown below.
DECLARE
BEGIN
IS_SENIOR_EMPLOYEE ;
END ;
Page 95
END ;
/
The greatest advantage of this modified parameterized version is that we can now run the same procedure
for several employees as shown below.
DECLARE
BEGIN
IS_SENIOR_EMPLOYEE(100) ;
IS_SENIOR_EMPLOYEE(105) ;
END ;
Page 96
After handling exceptions as above, run the following block to understand the effect.
DECLARE
BEGIN
IS_SENIOR_EMPLOYEE(10000) ;
IS_SENIOR_EMPLOYEE(105) ;
END ;
Page 97
END ;
/
The following code now tests the re-written procedure. It uses a new variable MESSAGE to retrieve the
output of the procedure. Then it prints the MESSAGE.
DECLARE
MESSAGE VARCHAR2(100) ;
BEGIN
IS_SENIOR_EMPLOYEE(10000, MESSAGE) ;
DBMS_OUTPUT.PUT_LINE(MESSAGE) ;
IS_SENIOR_EMPLOYEE(105, MESSAGE) ;
DBMS_OUTPUT.PUT_LINE(MESSAGE) ;
END ;
5. PL/SQL Functions
A PL/SQL function is like a PL/SQL procedure except that it must return a value. The general syntax of a
PL/SQL function is slightly different than a PL/SQL procedure. It only has an RETURN <DATATYPE>
clause at the end of the CREATE OR REPLACE statement.
CREATE OR REPLACE FUNCTION <FUNC_NAME> ( <PARAM1> [IN/OUT] <DATATYPE1>, ...)
RETURN <DATATYPE> IS
Declaration1 ;
Declaration2 ;
... ;
BEGIN
Statement1 ;
Statement2 ;
... ;
END ;
/
The effect of the RETURN statement is that a value is return after successful execution of the function.
That value will be used in the calling section.
Page 98
Let us re-write the same procedure used before as a function. In this task, the MSG variable used in the
procedure to output the message will be done by return statement. The following code shows the function
how to do this.
CREATE OR REPLACE FUNCTION GET_SENIOR_EMPLOYEE(EID IN VARCHAR2)
RETURN VARCHAR2 IS
JDATE DATE ;
YEARS NUMBER ;
MSG VARCHAR2(100) ;
BEGIN
SELECT HIRE_DATE INTO JDATE
FROM EMPLOYEES
WHERE EMPLOYEE_ID = EID ;
YEARS :=
A function must return a value of desired value from the BEGIN section
A function must also return a value of desired type from the EXCEPTION section.
Page 99
BEGIN
MESSAGE := GET_SENIOR_EMPLOYEE(10000) ;
DBMS_OUTPUT.PUT_LINE(MESSAGE) ;
MESSAGE := GET_SENIOR_EMPLOYEE(105) ;
DBMS_OUTPUT.PUT_LINE(MESSAGE) ;
END ;
Page 100
BEGIN
SELECT COUNT(*) INTO ECOUNT
FROM EMPLOYEES
WHERE EMPLOYEE_ID = EID ;
END ;
IF ECOUNT = 0 THEN
MSG := 'No employee found.' ;
ELSIF ECOUNT > 1 THEN
MSG := 'More than one employee found.' ;
ELSE
SELECT HIRE_DATE INTO JDATE
FROM EMPLOYEES
WHERE EMPLOYEE_ID = EID ;
YEARS :=
Inner PL/SQL blocks are like a general block that can have EXCEPTION section as well if
required.
In the modified function, exception handling is not required. Because this time number of
employees is first checked before retrieving employees hiring date. If no such data is found, then
the first SELECT COUNT(*) INTO ECOUNT query retrieves 0 into ECOUNT variable. So, no
exception occurs and therefore exception handling is also not required.
Practice
Page 101
an input VARCHAR2 value and checks whether the input can be converted to a valid number. If
the input can be converted to a valid number than ISNUMBER should return YES, otherwise
ISNUMBER should return NO.
6. Pl/SQL Triggers
A trigger is a PL/SQL stored block. It is like a function or a procedure. However, it is different than a
function or a procedure. To run a function or a procedure, it is explicitly called from a code. However, a
trigger is automatically run by the Oracle. It is not called from any code directly.
A trigger is automatically run by Oracle
Trigger is very useful when certain tasks are needed to be done after or before a DML operation. For
example, suppose we need to ensure that after every deletion of an employee records from the
EMPLOYEES table, the records of the deleted employee should go to a backup table. In such cases, a
trigger can be written which will perform the required task easily. Since, trigger will be automatically
called after the deletion operation; we need not to manually handle the writing backup records.
The general syntax of a trigger is like a procedure or a function except the header line.
CREATE OR REPLACE TRIGGER <TRIGGER_NAME>
(BEFORE | AFTER) (INSERT | UPDATE | DELETE)
[OF <COLUMN_NAME>]
ON <TABLE_NAME>
[FOR EACH ROW]
[WHEN <CONDITION>]
DECLARE
Declaration1 ;
Declaration2 ;
... ;
BEGIN
Statement1 ;
Statement2 ;
... ;
Page 102
EXCEPTION
Exception handing codes ;
END ;
/
Lets understand the trigger by writing our first trigger HELLO_WORLD trigger. This trigger will print
Hello World whenever an insertion statement is run on the table STUDENTS.
The following shows the trigger codes.
CREATE OR REPLACE TRIGGER HELLO_WORLD
AFTER INSERT
ON STUDENTS
DECLARE
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World');
END ;
/
Now, insert some rows (as shown below) and see what output comes!
INSERT INTO STUDENTS VALUES ('Fahim Hasan', 3.71);
INSERT INTO STUDENTS VALUES ('Ahmed Nahiyan', 3.80);
The trigger will run twice for the two insert statements and it will ouput Hello World.
Although, HELLO_WORLD trigger does not show the actual power of triggers, it demonstrates at least
the basic properties of a trigger which are following:
HELLO_WORLD trigger will run automatically by Oracle when an insert statement is run on the
table STUDENTS.
Page 103
Lets try several modification of the above trigger so that it runs in various settings. The following codes
show five variations of the HELLO_WORLD trigger.
--This trigger will run before insert on STUDENTS table
CREATE OR REPLACE TRIGGER HELLO_WORLD2
BEFORE INSERT
ON STUDENTS
DECLARE
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World2');
END ;
/
--This trigger will run after an insert or a delete statement on STUDENTS table
CREATE OR REPLACE TRIGGER HELLO_WORLD3
AFTER INSERT OR DELETE
ON STUDENTS
DECLARE
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World3');
END ;
/
--The following trigger will run after an update statement on STUDENTS table.
--Added with that, this trigger will only run when update is performed on the
--CGPA column.
CREATE OR REPLACE TRIGGER HELLO_WORLD4
AFTER UPDATE
OF CGPA
ON STUDENTS
DECLARE
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World4');
END ;
/
--The following trigger will run after an update operation on the STUDENTS table.
--Added with that, the trigger will run once for each row. The previous rows will
Page 104
--run once for the whole statement, where this trigger will run N times if N rows
--are affected by the SQL statement.
CREATE OR REPLACE TRIGGER HELLO_WORLD5
AFTER UPDATE
OF CGPA
ON STUDENTS
FOR EACH ROW
DECLARE
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World5');
END ;
/
Read the above five trigger codes and understand them. After you properly understand all five triggers,
lets now determine which trigger will be called by Oracle for the following five SQL statements.
INSERT INTO STUDENTS VALUES ('Shakib Ahmed', 3.63);
--This will run HELLO_WORLD, HELLO_WORLD2, HELLO_WORLD3
DELETE FROM STUDENTS WHERE CGPA < 3.65 ;
--This will run HELLO_WOLRD3
UPDATE STUDENTS SET CGPA = CGPA + 0.01 WHERE STUDENT_NAME LIKE '%Shakib%';
--This will run HELLO_WORLD4, but will not run HELLO_WORLD5!!! Why? Because
--HELLO_WORLD5 is declared with FOR EACH ROW clause. This means trigger should be
--run for each row affected. Since, the above statement does not update any row
--(as the previous DELETE operation already deleted that row from the table)
--it will not run HELLO_WORLD5!
UPDATE STUDENTS SET STUDENT_NAME = 'Fahim Ahmed'
WHERE STUDENT_NAME = 'Fahim Hasan' ;
--This will not run any trigger. Although HELLO_TRIGGER4 is declared to be run
--after an update operation, the trigger will not run because the update is done
--on the column STUDENT_NAME rather than CGPA
UPDATE STUDENTS SET CGPA = CGPA + 0.01 ;
--This will run both HELLO_WORLD4 and HELLO_WORLD5 trigger. However, HELLO_WORLD5
--will run twice! Why? Because two rows will be affected by the SQL statement!
Page 105
After analyzing the above five triggers, you should now understand the following:
The DML operation can be insert, update, delete or a combination of the three.
The trigger can be created such that it is run only once after an SQL statement or it is run once
per row affected by an SQL statement.
Classification of triggers
Trigger can be classified in following ways:
BEFORE trigger vs. AFTER trigger A BEFORE trigger is executed before a statement and an
AFTER trigger is executed after the statement.
ROW LEVEL trigger vs. STATEMENT LEVEL trigger A ROW LEVEL trigger is created when
FOR EACH ROW clause is specified in the trigger definition. In this case, the trigger will be
called after or before each row that is affected by the operation. A STATEMENT LEVEL trigger
is executed only once for each statement. So, if you issue a DML statement that affect N rows,
then a STATEMENT LEVEL trigger will be executed once while a ROW LEVEL trigger will be
executed N times. A STATEMENT LEVEL trigger must get executed once while a ROW
LEVEL trigger may not get executed at all if the DML operation does not affect any row!!!
Practice
Write a trigger HELLO_WORLD6 that will run after a deletion operation on the STUDENTS
table. The trigger should be a ROW LEVEL trigger.
Problem Example 1
Write a PL/SQL trigger LOG_CGPA_UPDATE. This trigger will log all updates done on the CGPA
column of STUDENTS table. The trigger will save current users name, current system date and time in a
log table named LOG_TABLE_CGPA_UPDATE.
Solution
The trigger required will be a STATEMENT LEVEL trigger. Because, it is required to run only per SQL
statement which will serve our purpose.
Page 106
After the trigger is created, issue the following update commands and then finally view the rows inserted
into LOG_TABLE_CGPA_UPDATE table.
--First update
UPDATE STUDENTS SET CGPA = CGPA + 0.01 ;
--Another update
UPDATE STUDENTS SET CGPA = CGPA - 0.01 ;
--View the rows inserted by the trigger
SELECT * FROM LOG_TABLE_CGPA_UPDATE
Page 107
Problem Example 2
Write a PL/SQL trigger BACKUP_DELETED_STUDENTS. This trigger will save all records that are
deleted from the STUDENTS table into a backup table named STUDENTS_DELETED. The trigger will
save students record along with current users name and current system date and time.
Solution
The trigger required will be a ROW LEVEL trigger. Because, it is required to run per row affected. Each
row that will be deleted will need to be saved in the backup table.
Lets first create the backup table STUDENTS_DELETED.
CREATE TABLE STUDENTS_DELETED(
STUDENT_NAME VARCHAR2(25),
CGPA NUMBER,
USERNAME VARCHAR2(25),
DATETIME DATE
) ;
The following code shows the trigger definition required to perform the specified task.
CREATE OR REPLACE TRIGGER BACKUP_DELETED_STUDENTS
BEFORE DELETE
ON STUDENTS
FOR EACH ROW
DECLARE
V_NAME VARCHAR2(25);
V_USERNAME VARCHAR2(25);
V_CGPA NUMBER;
V_DATETIME DATE;
BEGIN
V_NAME := :OLD.STUDENT_NAME ;
V_CGPA := :OLD.CGPA ;
V_USERNAME := USER ;
V_DATETIME := SYSDATE ;
INSERT INTO STUDENTS_DELETED VALUES (V_NAME,V_CGPA,V_USERNAME,V_DATETIME);
END ;
/
Page 108
Note the use of :OLD special reference. This reference is used to access the column values of currently
affected row by the DELETE operation. Like the :OLD reference, there is a :NEW reference that can be
used to retrieve the column values of the new row that will result after completion of the operation.
After the trigger is compiled and stored successfully, issue the following command and view the rows
inserted by the trigger.
--Delete the two rows
DELETE FROM STUDENTS WHERE CGPA < 3.85 ;
--View the rows inserted by the trigger
SELECT * FROM STUDENTS_DELETED ;
They are valid only for ROW LEVEL triggers! You are not allowed to use these in a
STATEMET LEVEL trigger.
For an update statement, :OLD is used to retrieve old values of columns while :NEW is used to
retrieve new values of columns.
For an insert statement, :OLD retrieves NULL values for all columns while :NEW can be used to
retrieve column values of the row
For a delete statement :NEW retrieves NULL values while :OLD can be used to retrieve column
values of the row
:NEW reference can be used to change column values of a row before it is going to be inserted in
the table. This will require a BEFORE trigger.
To understand the :OLD and :NEW reference more deeply, write the following trigger and issue the SQL
commands listed after the trigger.
CREATE OR REPLACE TRIGGER OLD_NEW_TEST
BEFORE INSERT OR UPDATE OR DELETE
ON STUDENTS
FOR EACH ROW
DECLARE
BEGIN
Page 109
Practice
Write a trigger that will save a student records in a table named LOW_CGPA_STUDENTS
which contain only one column to store students names. The trigger will work before an update
operation or an insert operation. Whenever the update operation results in a CGPA value less than
2.0, the trigger will be fired and the trigger will save the students name in the
LOW_CGPA_STUDENTS table. Similarly, when an insert operation inserts a new row with
CGPA less than 2.0, the corresponding row must be saved in the LOW_CGPA_STUDENTS
table.
Problem Example 3
Write a PL/SQL trigger CORRECT_STUDENT_NAME. This trigger will be used to correct the text case
of the student names when it is going to be inserted. So, this will be a BEFORE INSERT trigger. The
trigger will change the case of the students name to INITCAP format if it was not given by the user in
the INSERT statement. The trigger will thus ensure that all names stored in the STUDENTS table will be
in a consistent format.
CREATE OR REPLACE TRIGGER CORRECT_STUDENT_NAME
BEFORE INSERT
ON STUDENTS
FOR EACH ROW
DECLARE
BEGIN
:NEW.STUDENT_NAME := INITCAP(:NEW.STUDENT_NAME) ;
Page 110
END ;
/
--Issue the following SQL statements and then view the rows of STUDENTS table
INSERT INTO STUDENTS VALUES ('SHAkil ahMED', 3.80);
INSERT INTO STUDENTS VALUES ('masum billah', 3.60);
Note that the above trigger must be a BEFORE INSERT trigger. If you write an AFTER INSERT trigger,
then it will not work. Because in an AFTER INSERT trigger, you are not allowed to change values of the
:NEW row.
Practice
Write down a PL/SQL trigger on STUDENTS table. The trigger will ensure that whenever a new
row is inserted in the STUDENTS table, the name of the student contains only alphabetic
characters. Name your trigger INVALID_NAME. If the name is valid, then insertion should be
allowed. However, if the name is invalid, then insertion should be denied. To deny insertion, you
can throw an exception from the trigger that would halt the insertion operation.
So, to drop the trigger OLD_NEW_TEST from the database, issue the following command.
DROP TRIGGER OLD_NEW_TEST ;
Page 111