RE: 4031 - errors

From: <Jared.Still_at_radisys.com>
Date: Wed, 2 Jun 2004 14:31:54 -0700
Message-ID: <OF0B62BB58.22F0D81C-ON88256EA7.00760E82-88256EA7.00764492@radisys.com>

oracle-l-bounce_at_freelists.org wrote on 06/02/2004 02:03:38 PM:

> OK - here are some things that contributed to my problems and woes:
>
> 3) The other choke, gasp, dba had alot of dbms_outputs in procedure,
> functions except that he moved into production instead of commenting
them
> out.

Commenting them out is bad form for production code. A switch that can be set at runtime to enable/disable the debug code is quite a bit better.

The default of course should be false.

Jared

> one procedure that called another function which called another
> function, had more than 20 of these things. And yes same person who is
> updating
> across the links.....
>

Many functions is better than 1 big one. You just need to implement a trace mechanism to trace the call stack when the, *ahem*, debug flag is set.

Jared

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Wed Jun 02 2004 - 16:29:03 CDT