Have them return a cursor to you instead of dbms_output_get. There is
an example of how to bind to a cursor in the DBI man pages.
--eric
Jon Williams wrote:
>
> Have been using DBI with MySQL & Oracle for some time
> now. Recently, the powers that be (i.e my bosses)
> decided to use PL/SQL stored procedures for some of
> our rather complex queries. The PL/SQL guys are
> writing the query results to DBMS_OUTPUT. I cannot
> get to the query results via standard DBI syntax (i.e
> fetchrow_hashref or fetchrow_arrayref etc...). To get
> around this I've been using the 'dbms_output_get'
> method to retrieve query results:
>
> my @results = $db_handle -> func ( 'dbms_output_get'
> );
>
> Is this the preferred method of retrieving results
> from a PL/SQL procedure? Should the PL/SQL guys be
> giving me the results in some other fashion instead of
> writing to DBMS_OUTPUT? I scanned through a friends
> copy of "Programming the Perl DBI" and all I could
> find on the subject of DBMS_OUTPUT was a statement
> that said DBMS_OUTPUT is usually reserved for
> informational or trace messages from PL/SQL
> procedures.
>
> Any help you could provide would be great.
>
> Thanks.
>
> Jon.
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
