I thought unit testing *was* a good reason. :)
Jared
"Jamadagni, Rajendra" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/11/2002 11:51 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: RE: Database triggers question
Testing is a taboo ...
Well, they do the testing, but it is never enough. Usually a release is
followed by 2/3 emergency fixes for a real developer anyway. (before
anyone
jumps on this statement let me say is loudly that I have been a developer
for past 7 years and just joined the dark side.)
My problem is, " is it a good idea to have large triggers or package the
code and call it from triggers" ? Can someone throw a light on this?
Raj
______________________________________________________
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN
Inc.
QOTD: Any clod can have facts, but having an opinion is an art!
-----Original Message-----
Sent: Tuesday, June 11, 2002 1:27 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Hmmm.... Sounds like you have some real duhvelopers there.
Unit testing of code is much easier when it's outside of a trigger.
But the folks you're working with may not do unit testing.
Is it possible? ;)
Jared
*********************************************************************2
This e-mail message is confidential, intended only for the named recipient(s) above
and may contain information that is privileged, attorney work product or exempt from
disclosure under applicable law. If you have received this message in error, or are
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000
and delete this e-mail message from your computer, Thank you.
*********************************************************************2
