And the answer:

While one cannot pass back package-defined SQL variable types from Oracle stored procedures and functions, one can pass back cursors. And, you can define the cursor any way you see fit. So, here's how to accomplish the above.

First, you need to redefine the procedure to not return a "TABLE" type; rather, it should return a cursor (*note* I changed the procedure to a function because it seemed better that way now that it is just returning a var). 

CREATE OR REPLACE PACKAGE foo AS

  TYPE deptCurs IS REF CURSOR; 
  
  FUNCTION getAllDept RETURN foo.deptCurs;
END foo;

[download]
Your package body, then simply becomes: 
CREATE OR REPLACE PACKAGE BODY foo AS

   FUNCTION getDeptCurs RETURN foo.deptCurs IS
        crsr foo.deptCurs;
    BEGIN
          OPEN crsr FOR SELECT * FROM luDept;
          RETURN(crsr);
    END getDeptCurs;
END foo;

[download]
To get at this from Perl, you use the following code: 
my $dbh =DBI->connect('dbi:Oracle:host=hostname;sid=theSID',
       'user',
       'pass',
       {
           RaiseError => 1,
           AutoCommit => 0
       }) || die "Database connection not made because:\n\t$DBI::errst
+r\n";

my $deptRecords;

eval {
   my $func = $dbh->prepare(q{
       BEGIN
           :curs := foo.getDeptCurs();
       END;
   });
   
   # must specify the ora_type of ORA_RSET
   # so code knows it is a cursor
   $func->bind_param_inout(":curs ", \$deptRecords, 
                   0, { ora_type => ORA_RSET});    
   $func->execute;
   $func->finish;
};

if( $@ ) {
   warn "Execution of stored procedure failed because:\n\t$DBI::errstr
+\n$@";
}

while(my $hashRef = $deptRecords->fetchrow_hashref)
{
   foreach(keys %$hashRef)
   {
      print "$_ is $hashRef->{$_}\n";
   }
}

$deptRecords->finish;
$dbh->disconnect;

[download]

I'll leave this here for posterity just in case anyone else ever stumbles upon this particular problem and encounters Warnock's Dilemma.

enoch

In reply to Re: Binding "Out" Parameters to Table Types for Oracle PL/SQL Stored Procedures by enoch
in thread Binding "Out" Parameters to Table Types for Oracle PL/SQL Stored Procedures by enoch

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.