Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Triggers in package

Re: Triggers in package

From: shakespeare <whatsin_at_xs4all.nl>
Date: Mon, 19 Nov 2007 22:55:26 +0100
Message-ID: <47420657$0$244$e4fe514c@news.xs4all.nl>

"Maxim Demenko" <mdemenko_at_gmail.com> schreef in bericht news:474200D5.6040909_at_gmail.com...
> shakespeare schrieb:
>
>> BTW, I'm not a beginner as you did suggest. Just getting old and tired.
>> That's all....
>
> I didn't implied that, sorry if i expressed me not clear enough.

Reading is not my strongest point these days it seems... ;-)

>>
>> Putting trigger code in packages (but not the trigger itself) has one
>> advantage though: grouping all trigger code together in an easy to
>> maintain, easy to find module.
>
> This is the point, there i agree with you, however my understanding about
> OP question was - where the trigger can be *defined*. After rereading, i
> think however, yours is a valid interpretation - where the trigger code
> can be *put in* - in that case, your remark is of course appropriated -
> what i by first reading didn't recognized - again, i apologise for that.
>

No need for that... no problem!

> On the other side, the whole thread is drifted in direction of complex pl
> sql topics, which are (imho) interesting only after involved persons are
> familiar with fundamentals, which seems to be not the case - as OP stated,
> for that purpose, i still believe, the documentation is the best starting
> point.
>

You've got a point there!

> Best regards
>
> Maxim

Shakespeare Received on Mon Nov 19 2007 - 15:55:26 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US