This works oppositely to %FOUND it will return ‘TRUE’ if the most recent fetch operation could not able to fetch any record. It returns the Boolean result ‘TRUE’ if the most recent fetch operation fetched a record successfully, else it will return FALSE. Below are the different cursor attributes and their usage. These attributes give more information about the cursor operations.

In execution part, the declared cursor is opened, fetched and closed.īoth Implicit cursor and the explicit cursor has certain attributes that can be accessed.

The cursor is created for the ‘SELECT’ statement that is given in the cursor declaration.

In the above syntax, the declaration part contains the declaration of the cursor and the cursor variable in which the fetched data will be assigned.

Closing the CursorOnce all the record is fetched now, we need to close the cursor so that the memory allocated to this context area will be released.

This statement is same as ‘SELECT’ statement that fetches the record and assigns to the variable in the ‘INTO’ clause, but it will not throw any exceptions. Each fetch statement will fetch one active set and holds the information of that particular record. Fetching data from the cursor is a record-level activity that means we can access the data in a record-by-record way.

Fetching Data from the CursorIn this process, the ‘SELECT’ statement is executed and the rows fetched is stored in the allocated memory.

It will make the cursor ready to fetch the records.

Opening CursorOpening the cursor will instruct the PL/SQL to allocate the memory for this cursor.

The name of this context area is same as the cursor name.

Declaring the cursor Declaring the cursor simply means to create one named context area for the ‘SELECT’ statement that is defined in the declaration part.

The explicit cursor should be defined in the declaration section of the PL/SQL block, and it is created for the ‘SELECT’ statement that needs to be used in the code.īelow are steps that involved in working with explicit cursors.

Programmers are allowed to create named context area to execute their DML operations to get more control over it. We can refer only to the most recent cursor through the cursor attributes. These cursors cannot be named and, hence they cannot be controlled or referred from another place of the code. Whenever any DML operations occur in the database, an implicit cursor is created that holds the rows affected, in that particular operation. These cursors can also be named so that they can be referred from another place of the code. The set of rows the cursor holds is referred as active set. A cursor holds the rows returned by the SQL statement. PL/SQL allows the programmer to control the context area through the cursor. Oracle creates context area for processing an SQL statement which contains all information about the statement. A Cursor is a pointer to this context area.

What the line cursor called