Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 25 views

    Cursors

    Uploaded by

    Janitha Chamaka
    1) A cursor is a temporary work area in memory that holds data retrieved from a database query. It allows processing of query results one row at a time. 2) There are two types of cursors: implicit cursors are created automatically for DML statements, explicit cursors must be declared for queries returning multiple rows. 3) Cursors store query results in memory and allow sequential access of rows through opening, fetching, and closing operations.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Cursors

    Uploaded by

    Janitha Chamaka
    25 views17 pages
    1) A cursor is a temporary work area in memory that holds data retrieved from a database query. It allows processing of query results one row at a time. 2) There are two types of cursors: implicit cursors are created automatically for DML statements, explicit cursors must be declared for queries returning multiple rows. 3) Cursors store query results in memory and allow sequential access of rows through opening, fetching, and closing operations.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1) A cursor is a temporary work area in memory that holds data retrieved from a database query. It allows processing of query results one row at a time. 2) There are two types of cursors: implicit cursors are created automatically for DML statements, explicit cursors must be declared for queries returning multiple rows. 3) Cursors store query results in memory and allow sequential access of rows through opening, fetching, and closing operations.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    25 views17 pages

    Cursors

    Uploaded by

    Janitha Chamaka
    1) A cursor is a temporary work area in memory that holds data retrieved from a database query. It allows processing of query results one row at a time. 2) There are two types of cursors: implicit cursors are created automatically for DML statements, explicit cursors must be declared for queries returning multiple rows. 3) Cursors store query results in memory and allow sequential access of rows through opening, fetching, and closing operations.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    You are on page 1of 17

    CURSORS

    S.Naji
    naji@nsbm.lk
    Cursors
     A cursor is a temporary work area created in the
    system memory when a SQL statement is executed.
    A cursor contains information on a select statement
    and the rows of data accessed by it. This temporary
    work area is used to store the data retrieved from
    the database, and manipulate this data. A cursor can
    hold more than one row, but can process only one
    row at a time. The set of rows the cursor holds is
    called theactive set.
    Types of cursors
     There are two types of cursors in PL/SQL:
     Implicit cursors:
     These are created by default when DML statements like, INSERT,
    UPDATE, and DELETE statements are executed. They are also created
    when a SELECT statement that returns just one row is executed.

     Explicit cursors:
     They must be created when you are executing a SELECT statement that
    returns more than one row. Even though the cursor stores multiple records,
    only one record can be processed at a time, which is called as current row.
    When you fetch a row the current row position moves to next row.
     Both implicit and explicit cursors have the same functionality, but they
    differ in the way they are accessed.
    S.No Attribute & Description
    %FOUND
    Returns TRUE if an INSERT, UPDATE, or
    1 DELETE statement affected one or more rows or a
    SELECT INTO statement returned one or more
    rows. Otherwise, it returns FALSE.
    %NOTFOUND
    The logical opposite of %FOUND. It returns TRUE
    2 if an INSERT, UPDATE, or DELETE statement
    affected no rows, or a SELECT INTO statement
    returned no rows. Otherwise, it returns FALSE.
    %ISOPEN
    Always returns FALSE for implicit cursors, because
    3
    Oracle closes the SQL cursor automatically after
    executing its associated SQL statement.
    %ROWCOUNT
    Returns the number of rows affected by an INSERT,
    4
    UPDATE, or DELETE statement, or returned by a
    SELECT INTO statement.
    Implicit Cursor

    DECLARE total_rows number(2);


    BEGIN
    UPDATE customers SET salary = salary + 500;
    IF sql%notfound THEN dbms_output.put_line('no
    customers selected’);
    ELSIF sql%found THEN total_rows := sql%rowcount;
    dbms_output.put_line( total_rows || ' customers
    selected ‘);
    END IF;
    END; /
    Explicit Cursor
     CURSOR cursor_name
    IS
    SELECT_statement;

    Example
    CURSOR c1
    IS
    SELECT course_number
    from courses_tbl
    where course_name = name_in;
    DECLARE c_id customers.id%type;
    c_name customers.name%type;
    c_addr customers.address%type;
    CURSOR c_customers is SELECT id, name, address
    FROM customers;
    BEGIN OPEN c_customers;
    LOOP FETCH c_customers into c_id, c_name,
    c_addr;
    EXIT WHEN c_customers%notfound;
    dbms_output.put_line(c_id || ' ' || c_name || '
    ' || c_addr);
    END LOOP;
    CLOSE c_customers;
    END; /
    Cursor Declaration
     DECLARE
     CURSOR employee_cur IS
     SELECT * FROM employee
     FOR UPDATE OF salary;
     BEGIN
     FOR employee_rec IN employee_cur
     LOOP
     UPDATE employee
     SET salary = 10000
     WHERE CURRENT OF employee_cur;
     END LOOP;
     END;
     /
    Check the answer

     Select * from employee;


    Cursor Declaration (Example)
     DECLARE
     v_salary employee.salary%TYPE;

     CURSOR c_Registeredemployee IS
     SELECT *
     FROM employee
     WHERE id IN ('01')
     FOR UPDATE OF salary;

    Continue….
     BEGIN
     -- Set up the cursor fetch loop.
     v_salary := 100;
     FOR v_employeeInfo IN c_Registeredemployee LOOP

     -- Update the row we just retrieved from the cursor.


     UPDATE employee
     SET salary = salary + v_salary
     WHERE CURRENT OF c_Registeredemployee;
     END LOOP;

     -- Commit our work.


     COMMIT;
     END;
     /
    Record

    • Table-based
    • Cursor-based records
    • User-defined records

    • row%type is used to access first 2


    records (table,cursor)
    Table based Record
    DECLARE
    customer_rec customers%rowtype;
    BEGIN
    SELECT * into customer_rec FROM customers WHERE
    id = 5;
    dbms_output.put_line('Customer ID: ' ||
    customer_rec.id);
    dbms_output.put_line('Customer Name: ' ||
    customer_rec.name);
    dbms_output.put_line('Customer Address: ' ||
    customer_rec.address);
    dbms_output.put_line('Customer Salary: ' ||
    customer_rec.salary);
    END; /
    Cursor Based Record
    DECLARE CURSOR
    customer_cur is
    SELECT id, name, address FROM customers;
    customer_rec customer_cur%rowtype;
    BEGIN
    OPEN customer_cur;
    LOOP FETCH customer_cur into customer_rec;
    EXIT WHEN customer_cur%notfound;
    DBMS_OUTPUT.put_line(customer_rec.id || ' '
    || customer_rec.name);
    END LOOP;
    END; /
    Commit
     Just the Word commit used to save the current
    changes permernantly

     Commit

     Set autocommit on (to on the Auto commit option)


    Rollback
     To Cancel the Last changes

     Rollback

     ** If you used Commit , then it cannot be Rolled


    back
    Save point
     Format

     SAVEPOINT S1;

     USING ROLLBACK WITH SAVE POINT

     ROLLBACK TO S1;

    You might also like