Re: solution has been found but till no explanation
From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 15 Mar 2001 11:13:13 -0000
Message-ID: <984654605.11115.0.nnrp-09.9e984b29_at_news.demon.co.uk>
Date: Thu, 15 Mar 2001 11:13:13 -0000
Message-ID: <984654605.11115.0.nnrp-09.9e984b29_at_news.demon.co.uk>
You certainly should not be able to
enable or disable a trigger in the
middle of a transaction - if that's
[Quoted] what you meant - as the command:
[Quoted] alter trigger xxx disable;
will issue an implicit commit, and
end the current transaction.
-- Jonathan Lewis Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk Practical Oracle 8i: Building Efficient Databases Publishers: Addison-Wesley Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html Alexander Chupin wrote in message <98q7bq$nlp$1_at_soap.pipex.net>...Received on Thu Mar 15 2001 - 12:13:13 CET
>> I guess that Oracle has to decide the locking
>> strategy based on the structure of the trigger
>> rather than the actual values coming in.
>
>Thank you very much indeed :-)
>btw, I've one question more.
>I mentioned taht Oracle allows make trigger (discribed in
>previous letters) enabled or disabled during transaction
>in which as you supposed the trigger body is quite
>important part. I wonder - is it correct in your opinion?
>
>WBR, Alexander Chupin
>
>
>