RE: When and when not to create SP/triggers

Beg pardon. I meant to say at most one SP _per_ trigger. I can also see the benefit of modularizing stored procedures, but it can make debugging a bit more difficult, so there's something of a trade-off there. } ---------- } From: Felix Koshy Mathews[SMTP:fmathews@systems.DHL.COM] } Reply To: fmathews@systems.DHL.COM } Sent: Tuesday, December 30, 1997 7:53 PM } To: Thomas J. Girsch } Cc: informix-list@rmy.emory.edu } Subject: Re: When and when not to create SP/triggers } } I won't agree with that "at most one SP for every trigger", when you } implement } business rules using triggers & SPs, you could avoid duplication of } common logic } by designing/coding them into SPs with modularized common logic. } These common } business logic can be enforced in triggers and programs by executing } those SPs. } You can call one junk-SP with all values which eventually calls } required SPs, } which I won't recommend, so why not call individual SPs as you need } them ?