Pass a record type vaiable in out parameter of a function in a package

Question

Hi All,
1.I have created a ecod inside a package.
2.Then created a function which has a out parameter of the above record.
3.Now package body i'm creating a dynamic cursor .
4.My equirement is to fetch this dynamic cursor's value into the out parameter of the function.
I have created the below code for 1,2 and 3 but not getting how to achive the point 4.
create package pkg
type t_rec is recod (id number,id_name varchar2(10));
type t_data is table of t_rec index by binary_integer;
act_data t_data;
funcion return_data is (dept in number,region in number,o_rec out t_data) return boolean;
end pkg;
create package body pkg
funcion return_data is (dept in number,region in number,o_rec out t_data) return boolean is
p_cur sys_refcursor;
l_text varchar2(100);
begin
-- As per my requirement i have built a dynamic l_text which contains where clause by taking dept and region values.In actual i have nearly 10 in paramaters with >which i'm building a dynamic where clause in l_text. So i'm using a ref cursor.
open p_cur for 'select id,id_name from tab1'||l_text';
fetch p_cur bulk collect into act_data;
exception ....
end pkg;Now as per the code snippet i could fetch all the rows returned by p_cur into act_data.
But how i will pass it though out parameter in the function which i will use somewhere in front end to show data.
Please help me in this.
Thanks in advance.

Answer 1

bp wrote:
i need to create the where clause one the basis of the values of IN parameters.Sometimes i need to take count of the data on the basis of the IN parameters and if one of the conditions return value i will build where clause with those parameters.Please google and read up on the importance of creating shareable SQL - which needs to be done using bind variables.
The ref cursor interface in PL/SQL only support a static/fixed number of bind variables. So if you want to create cursors with variable number of bind values, you need to use conditional processing. E.g.
SQL> create or replace procedure EmpFilter( c OUT sys_refcursor, nameFilter varchar2, jobFilter varchar2 ) is
  2          sqlSelect       varchar2(32767);
  3  begin
  4          --// we pretend to built a dynamic SQL statement - so the table
  5          --// name and so on is "unknown"
  6          sqlSelect := 'select * from emp ';
  7          case
  8                  when nameFilter is null and jobFilter is null then
  9                          open c for sqlSelect;
10
11                  when nameFilter is null and jobFilter is not null then
12                          sqlSelect := sqlSelect||'where job like :filter';
13                          open c for sqlSelect  using jobFilter;
14
15                  when nameFilter is not null and jobFilter is null then
16                          sqlSelect  := sqlSelect||'where ename like :filter';
17                          open c for sqlSelect  using nameFilter;
18
19                  when  nameFilter is not null and jobFilter is not null then
20                          sqlSelect  := sqlSelect||'where ename like :filter1 and job like :filter2';
21                          open c for sqlSelect  using nameFilter, jobFilter;
22
23          end case;
24
25          DBMS_OUTPUT.put_line( 'Dynamic SQL: '||sqlSelect );
26  end;
27  /
Procedure created.
SQL>
SQL>
SQL> var c refcursor
SQL> begin
  2          EmpFilter( :c, 'A%', null );
  3  end;
  4  /
Dynamic SQL: select * from emp where ename like :filter
PL/SQL procedure successfully completed.
SQL> print c
     EMPNO ENAME      JOB              MGR HIREDATE                   SAL       COMM     DEPTNO
      7499 ALLEN      SALESMAN        7698 1981/02/20 00:00:00       1600        300         30
      7876 ADAMS      CLERK           7788 1987/05/23 00:00:00       1100                    20
SQL>
SQL> begin
  2          EmpFilter( :c, null, 'ANALYST' );
  3  end;
  4  /
Dynamic SQL: select * from emp where job like :filter
PL/SQL procedure successfully completed.
SQL> print c
     EMPNO ENAME      JOB              MGR HIREDATE                   SAL       COMM     DEPTNO
      7788 SCOTT      ANALYST         7566 1987/04/19 00:00:00       3000                    20
      7902 FORD       ANALYST         7566 1981/12/03 00:00:00       3000                    20
SQL>And this approach is for external clients - where a Visual Basic or Java client program calls the database, executes the stored procedure, and receives a cursor handle in turn. And the client then fetches the output of this cursor and process it.
There is no need to return a record type of any sorts. The client wants the cursor handle as that is the optimal and best interface for the client to receive database data.
If the caller is not an external client, but another PL/SQL procedure, then this approach does not make much sense.
It is important that you understand basic Oracle concepts and fundamentals. What a cursor is. What the best way is to process Oracle data. How to best use the basic features of Oracle. Without that basic understanding, you as good as a low hour Cessna pilot getting into an Airbus A400M - where the Cessna pilot would not even be able to start a single engine, never mind get the plane in the air.
Likewise, without a basic understanding of Oracle cursors and fundamentals, you will be unable to code even a single line of sensible code. Not because you are a bad programmer. Even the best programmer in the world will be unable to write decent code, if the programmer has no idea how the environment works, what the concepts and fundamentals are. But it is fair to expect that a good programmer will no write such code, understand that there is a lack of knowledge, and address that accordingly.