Ex No: 7

Loops using ERROR Handling

LOOP

implements a simple loop construct, enabling repeated execution of the statement

list, which consists of one or more statements, each terminated by a semicolon ( ;) statement delimiter. The statements within the loop are repeated until the loop is terminated. Usually, this is accomplished with a LEAVE statement. Within a stored function, RETURN can also be used, which exits the function entirely. LOOP Syntax

[begin_label:] LOOP statement_list END LOOP [end_label] Example 1:

DELIMITER $$ DROP PROCEDURE IF EXISTS display$$ CREATE PROCEDURE display(no int) BEGIN DECLARE count INT DEFAULT 0; display: LOOP SET count=count+1; select count; IF count=no THEN LEAVE display; END IF; END LOOP display; END$$ DELIMITER ;

Call Procedure call display(5);

Example 2: RAISE- APPLICATION ERROR. The RAISE_APPLICATION_ERROR procedure raises an exception based on a userprovided error code and message
DELIMITER $$ CREATE PROCEDURE raise_application_error(IN CODE INTEGER, IN MESSAGE VARCHAR(255)) SQL SECURITY INVOKER DETERMINISTIC BEGIN CREATE TEMPORARY TABLE IF NOT EXISTS RAISE_ERROR(F1 INT NOT NULL); SELECT CODE, MESSAGE INTO @error_code, @error_message; INSERT INTO RAISE_ERROR VALUES(NULL); END; $$

CREATE PROCEDURE get_last_custom_error() SQL SECURITY INVOKER DETERMINISTIC BEGIN SELECT @error_code, @error_message; END; $$ DELIMITER ;

CALL raise_application_error(1234, 'Custom message'); CALL get_last_custom_error();

Example : table which stores only odd numbers.

CREATE TABLE ex1(only_odd_numbers INT UNSIGNED); DELIMITER $$

CREATE TRIGGER ex1_bi BEFORE INSERT ON ex1 FOR EACH ROW BEGIN IF NEW.only_odd_numbers%2 != 0 THEN CALL raise_application_error(3001, 'Not odd number!'); END IF; END $$ CREATE TRIGGER ex1_bu BEFORE UPDATE ON ex1 FOR EACH ROW BEGIN IF NEW.only_odd_numbers%2 != 0 THEN CALL raise_application_error(3001, 'Not odd number!'); END IF; END $$ DELIMITER ;

mysql> INSERT INTO ex1 VALUES(2); Query OK, 1 row affected (0.01 sec) mysql> INSERT INTO ex1 VALUES(3); ERROR 1048 (23000): Column 'F1' cannot be null mysql> CALL get_last_custom_error(); +-------------+-----------------+ | @error_code | @error_message | +-------------+-----------------+ | 3001 | Not odd number! | +-------------+-----------------+ 1 row in set (0.00 sec) Query OK, 0 rows affected (0.00 sec) mysql> SELECT \* FROM ex1; +------------------+ | only_odd_numbers | +------------------+ | 2 | +------------------+ 1 row in set (0.00 sec)

mysql> CREATE TABLE Employee( -> id int, -> first_name VARCHAR(15), -> last_name VARCHAR(15),

-> -> -> -> -> -> );

start_date end_date salary city description

DATE, DATE, FLOAT(8,2), VARCHAR(10), VARCHAR(15)

mysql> insert into Employee(id,first_name, last_name, start_date, end_Date,s

alary,City,Description)values (1,'Jason','Martin', 1234.56, 'Toronto', 'Programmer'); '19960725', '20060725',

Query OK, 1 row affected (0.00 sec) mysql> select * from Employee; +------+------------+-----------+------------+------------+---------+-----------+-------------+ | id | first_name | last_name | start_date | end_date | salary | city | description | +------+------------+-----------+------------+------------+---------+-----------+-------------+ | 1 | Jason | Martin | 1996-07-25 | 2006-07-25 | 1234.56 | Toronto | Programmer | | 2 | Alison | Mathews | 1976-03-21 | 1986-02-21 | 6661.78 | Vancouver | Tester | | 3 | James | Smith | 1978-12-12 | 1990-03-15 | 6544.78 | Vancouver | Tester | | 4 | Celia | Rice | 1982-10-24 | 1999-04-21 | 2344.78 | Vancouver | Manager | | 5 | Robert | Black | 1984-01-15 | 1998-08-08 | 2334.78 | Vancouver | Tester | | 6 | Linda | Green | 1987-07-30 | 1996-01-04 | 4322.78 | New York | Tester | | 7 | David | Larry | 1990-12-31 | 1998-02-12 | 7897.78 | New York | Manager | | 8 | James | Cat | 1996-09-17 | 2002-04-15 | 1232.78 | Vancouver | Tester | +------+------------+-----------+------------+------------+---------+-----------+-------------+ 8 rows in set (0.01 sec)
mysql> delimiter $$ mysql> CREATE PROCEDURE myProc (in_customer_id INT) -> BEGIN -> -> DECLARE l_first_name VARCHAR(30); -> DECLARE l_id INT; -> DECLARE l_city VARCHAR(30); -> DECLARE l_department_count INT; -> DECLARE no_more_departments INT; -> -> DECLARE dept_csr CURSOR FOR -> SELECT id,first_name, city -> FROM employee; -> -> DECLARE CONTINUE HANDLER FOR NOT FOUND SET no_more_departments=1; -> -> SET no_more_departments=0; -> OPEN dept_csr; -> dept_loop:WHILE(no_more_departments=0) DO -> FETCH dept_csr INTO l_id,l_first_name,l_city; -> IF no_more_departments=1 THEN

-> LEAVE dept_loop; -> END IF; -> SET l_department_count=l_department_count+1; -> select l_id,l_first_name,l_city; -> END WHILE dept_loop; -> CLOSE dept_csr; -> SET no_more_departments=0; -> -> END$$ Query OK, 0 rows affected (0.00 sec) mysql> delimiter ; mysql> mysql> call myProc(1);

Exception Raised when ...

ACCESS_INTO_NULL

Your program attempts to assign values to the attributes of an uninitialized (atomically null) object.
CASE_NOT_FOUND

None of the choices in the WHEN clauses of a CASE statement is selected, and there is no ELSE clause.
COLLECTION_IS_NULL

Your program attempts to apply collection methods other than EXISTS to an uninitialized (atomically null) nested table or varray, or the program attempts to assign values to the elements of an uninitialized nested table or varray.
CURSOR_ALREADY_OPEN

Your program attempts to open an already open cursor. A cursor must be closed before it can be reopened. A cursor FOR loop automatically opens the cursor to which it refers. So, your program cannot open that cursor inside the loop.
DUP_VAL_ON_INDEX

Your program attempts to store duplicate values in a database column that is constrained by a unique index.
INVALID_CURSOR

Your program attempts an illegal cursor operation such as closing an unopened cursor.
INVALID_NUMBER

In a SQL statement, the conversion of a character string into a number fails because the string does not represent a valid number. (In procedural statements, VALUE_ERROR is raised.) This exception is also raised when the LIMIT-clause expression in a bulk FETCH statement does not evaluate to a positive number.
LOGIN_DENIED

Your program attempts to log on to Oracle with an invalid username and/or password.
NO_DATA_FOUND

A SELECT INTO statement returns no rows, or your program references a deleted element in a nested table or an uninitialized element in an index-by table. SQL aggregate functions such as AVG and SUM always return a value or a null. So, a SELECT INTO statement that calls an aggregate function never raises NO_DATA_FOUND. The FETCH statement is expected to return no rows eventually, so when that happens, no exception is raised.
NOT_LOGGED_ON

Your program issues a database call without being connected to Oracle.

PROGRAM_ERROR

PL/SQL has an internal problem.

ROWTYPE_MISMATCH

The host cursor variable and PL/SQL cursor variable involved in an assignment have incompatible return types. For example, when an open host cursor variable is passed to a stored subprogram, the return types of the actual and formal parameters must be compatible.
SELF_IS_NULL

Your program attempts to call a MEMBER method on a null instance. That is, the builtin parameter SELF (which is always the first parameter passed to a MEMBER method) is null.
STORAGE_ERROR

PL/SQL runs out of memory or memory has been corrupted.

SUBSCRIPT_BEYOND_COUNT

Your program references a nested table or varray element using an index number larger than the number of elements in the collection.

SUBSCRIPT_OUTSIDE_LIMIT

Your program references a nested table or varray element using an index number (-1 for example) that is outside the legal range.
SYS_INVALID_ROWID

The conversion of a character string into a universal rowid fails because the character string does not represent a valid rowid.
TIMEOUT_ON_RESOURCE

A time-out occurs while Oracle is waiting for a resource.

TOO_MANY_ROWS

A SELECT INTO statement returns more than one row.

VALUE_ERROR

An arithmetic, conversion, truncation, or size-constraint error occurs. For example, when your program selects a column value into a character variable, if the value is longer than the declared length of the variable, PL/SQL aborts the assignment and raises VALUE_ERROR. In procedural statements, VALUE_ERROR is raised if the conversion of a character string into a number fails. (In SQL statements, INVALID_NUMBER is raised.)
ZERO_DIVIDE

Your program attempts to divide a number by zero.