Re: Oracle Development - Best Practice
- From: Pete Finnigan <oracle_list@xxxxxxxxxxxxxxxxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Sun, 8 Feb 2004 21:51:53 +0000
>Provide a standard set of code fragments to developers to be executed
>immediately after the module entry point and before all module exit points
>(including error handlers).
>
Hi Tim,
I do the same with PL/SQL and indeed in my C code as well. I always add
a standard prolog, epilog and error handler. I also find it useful to
instrument code with my own trace package (not to replace a debugger)
but for use after go live so that users can turn on trace so that its
sometimes easier to see what is happening with issues and errors that
they report. My trace package is normally null routed and can be written
to file or screen and includes error levels that can be set - it reports
timing and function name, line number etc. I use editor macros to
generate prolog, epilog and error handlers and also to instrument
certain constructs so its not too much effort to use it typing wise.
I read a paper by Steve Feuerstein a while back where he extolled the
virtues of instrumenting code, PL/SQL in particular for the purpose of
after sales support - sorry I cannot find the URL with a casual search
now.
hth
kind regards
Pete
--
Pete Finnigan
email:pete@xxxxxxxxxxxxxxxx
Web site: http://www.petefinnigan.com - Oracle security audit specialists
Book:Oracle security step-by-step Guide - see http://store.sans.org for details.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
