Hi all, Does anyone have any recommendations for db trigger size?
Some developers here write triggers that have 400-700 lines in them. I am pushing them to write a package and call that package from within the trigger. But to put this argument forward, I need to give some good reasoning and that's why I am looking for some recommendations. Some of these triggers are on tables that are most active in the database (i.e. DML ALL the time) and none of the triggers are pinned. Thanks in advance 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!
*********************************************************************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
