Oracle
  Home arrow Oracle arrow Page 4 - Working with REF CURSOR in PL/SQL
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBMŪ developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
Google.com  
ORACLE

Working with REF CURSOR in PL/SQL
By: Jagadish Chatarji
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 245
    2007-02-12


    Table of Contents:
  • Working with REF CURSOR in PL/SQL
  • Working with RECORD and REF CURSOR
  • Working with more than one query with the same REF CURSOR
  • Dealing with REF CURSOR in the sub-programs of a PL/SQL block

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    Working with REF CURSOR in PL/SQL - Dealing with REF CURSOR in the sub-programs of a PL/SQL block
    ( Page 4 of 4 )

    Sub-programs can also be called sub-routines.  These are nothing but the divisions of the main program.  These divisions are named and are executed when they are called by name from the main program.  They will not get executed unless they are called. 

    The following is an example:

    declare
      type r_cursor is REF CURSOR;
      c_emp r_cursor;
      type rec_emp is record
      (
        name  varchar2(20),
        sal   number(6)
      );
      er rec_emp;
      procedure PrintEmployeeDetails is
      begin
        loop
          fetch c_emp into er;
          exit when c_emp%notfound;
          dbms_output.put_line(er.name || ' - ' || er.sal);
        end loop;
      end;
    begin
      for i in (select deptno,dname from dept)
      loop
        open c_emp for select ename,sal from emp where deptno = i.deptno;
        dbms_output.put_line(i.dname);
        dbms_output.put_line('--------------');
        PrintEmployeeDetails;
        close c_emp;  
      end loop;
    end;

    In the above program, the sub-routine is named "PrintEmployeeDetails."  You can observe that I am executing (or calling) the sub-routine from within the loop as follows:

      for i in (select deptno,dname from dept)
      loop
         
    .
         
    .
         
    PrintEmployeeDetails;
          .
          .
      end loop;

    According to the above loop, the sub-routine gets executed for every iteration, which displays the employee information for the respective department.

    Passing REF CURSOR as parameters to sub-programs

    In the previous section, we already started working with sub-programs (or sub-routines).  In this section, I shall extend the same with the concept of "parameters" (or arguments).  Every sub-program (or sub-routine) can accept values passed to it in the form of "parameters" (or arguments).  Every parameter is very similar to a variable, but gets declared as part of a sub-program.

    Let us consider the following program:

    declare
      type r_cursor is REF CURSOR;
      c_emp r_cursor;
      type rec_emp is record
      (
        name  varchar2(20),
        sal   number(6)
      );
      procedure PrintEmployeeDetails(p_emp r_cursor) is
        er rec_emp;
      begin
        loop
          fetch p_emp into er;
          exit when p_emp%notfound;
          dbms_output.put_line(er.name || ' - ' || er.sal);
        end loop;
      end;
    begin
      for i in (select deptno,dname from dept)
      loop
        open c_emp for select ename,sal from emp where deptno = i.deptno;
        dbms_output.put_line(i.dname);
        dbms_output.put_line('--------------');
        PrintEmployeeDetails(c_emp);
        close c_emp;  
      end loop;
    end;

    From the above program, you can observe the following declaration:

      procedure PrintEmployeeDetails(p_emp r_cursor) is

    In the above declaration, "PrintEmployeeDetails" is the name of the sub-routine which accepts "p_emp" as a parameter (of type "r_cursor") and we can use that parameter throughout that sub-routine.

    I hope you enjoyed the article and any comments, suggestions, feedback, bugs, errors, enhancements etc. are highly appreciated at http://jagchat.spaces.live.com



     
     
    >>> More Oracle Articles          >>> More By Jagadish Chatarji
     

       

    ORACLE ARTICLES

    - Oracle's Turn to Play in the Sun
    - Implementing and Using Oracle`s Restore Poin...
    - Tuning PL/SQL Code
    - Debugging PL/SQL Code
    - Testing PL/SQL Code
    - Working With PL/SQL Code
    - Conditional Compilation for Oracle Database ...
    - Compile-Time Warnings for Oracle DB 10g
    - Compiling PL/SQL Code for an Oracle Database
    - Troubleshooting PL/SQL Code
    - Managing PL/SQL Code
    - Data Manipulation and More for HTML DB Appli...
    - Oracle Database Fundamentals
    - Adding Processes to HTML DB Applications
    - Adding Computations, Processes, and Validati...





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 4 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek