I apologize for this late response, but I've been a bit busy lately. You should be aware there are some potentially severe limitations on DBMS_OUTPUT. You are limited to 1M total in the buffer (used to be 2M). Each line is limited to 255 bytes. The output is not available until the execution unit writing it exits.
The $dbh->func() subfunctions are documented in 'perldoc DBD::Oracle' and are probably the preferred way to interact with DBMS_OUTPUT from DBI. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "Jon Williams" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 05, 2001 05:50 Subject: DBI With Oracle & PL/SQL > 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
