Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Mutating table inside trigger
Hans Börjesson wrote:
> Hi!
>
[]
>
>>But a bigger issue here is what appears to be a design error. Why should >>inserting one record in a table cause other records to be inserted into >> the same >>table? Consider this in terms of normalization and business logic. For >> example >>why is it that the procedure inserting the original record isn't just >> adding the >>additional records too? >>
But the question arises: Why do you want to hardcode business logic into the database? This should, as Daniel pointed out, be done at the application level, or maybe the middle level in a 3-tier architecture. You are making this harder by trying to do it in the database.
If your application is designed well, you should be able to do this in the application. I've worked on susch systems (precisely of the type you describe: customer ordering with bundled products). There are much better, more flexible ways to do this.
Drop me an email to discuss off-line.
-- Ed Prochak running: http://www.faqs.org/faqs/running-faq/ family: http://web.magicinterface.com/~collins -- "Two roads diverged in a wood and I I took the one less travelled by and that has made all the difference." robert frostReceived on Mon Mar 10 2003 - 10:45:41 CST
![]() |
![]() |