From: John Finlay
Date: Thu, Jun 24, 2010 at 23:18
Subject: PLOG_OUT_DBMS_OUTPUT
To: guillaume
Guillaume,
I've attached an update (actually a replacement) for the
PLOG_OUT_DBMS_OUTPUT.LOG procedure.
The original version indented the message text to whatever length the header
(timestamp-severity-callstack) was, which made for some strange output like
14:58:12.73-FATAL-block:2->MORE.STUFF:27->EVENMORE.STUFF:128 Here is my
message that wraps at 100
characters
which looks kind of weird
and wastes a
lot of space. Big deal o
n the space,
but still...
Unfortunately, the original code used the pCTX.DBMS_OUTPUT_WRAP value as the
maximum length of the line (as it should), so if the
timestamp-severity-callstack is greater than 100 characters, there's no room
left for the message, and the procedure loops and throws an ORU-10027 buffer
overflow error.
This new version uses a constant indent (of 3 spaces), so wrapped output now
looks like
14:58:12.73-FATAL-block:2->MORE.STUFF:27->EVENMORE.STUFF:128 Here is my
message that wraps at 100
characters which looks much nicer and is easier to read because there is
actually some length to
the message line's output and at least it never explodes.
John Finlay
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Log4plsql-all-info mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
log4plsq : http://log4plsql.sourceforge.net
