Hi!
If it does, and the proc if wrapped, you could also hack around by putting a
trigger on some table which gets updated/inserted/deleted few times during
the proc and put dbms_output.disable in it. I've never tried it myself, but
it could work as well...
Tanel.
- Original Message -
talk about unprofessional... this stuff should never go into production. which vendor
is it? ill aviod?
cant you juse set serveroutput off? to turn off the output?
From: Kevin Toepke [EMAIL PROTECTED]
Date: 2003/08/26 Tue PM 01:44:42 EDT
To: Multiple recipients of list ORACLE-L [EMAIL
Forgot the smiley!
And, to make up for that, I ran a simple test and found that 'set
serveroutput off' solves the problem.
My code:
BEGIN
dbms_output.put_line('sysdate: ' || sysdate);
END;
/
with serveroutput on started dumping data to the screen in about 5 seconds.
With serveroutput off I
looks like internally from proc its setting dbms_output.enable();
-ak
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 11:04 AM
talk about unprofessional... this stuff should never go into production.
which vendor is it?
