Re: solution has been found but till no explanation
From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 15 Mar 2001 17:20:48 -0000
Message-ID: <984676987.22123.0.nnrp-07.9e984b29_at_news.demon.co.uk>
Date: Thu, 15 Mar 2001 17:20:48 -0000
Message-ID: <984676987.22123.0.nnrp-07.9e984b29_at_news.demon.co.uk>
Okay -
[Quoted] So we have a trigger on the table.
Session 1 inserts a row
the trigger fires
Session 2 disables the trigger
ouch - I would have thought that there
would have been a dependency issue
that stopped this happening.
Session 1 inserts a second row
the behaviour is different because the trigger does not fire.
Session 1 commits.
[Quoted] I am slightly surprised that Session 2 can disable the trigger whilst there is an active transaction on the table. It doesn't seem to be a reasonable [Quoted] thing to do. (On the other hand, I don't expect developers to be hacking the live system whilst users are processing data ;)
-- 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 <98qbkm$pks$1_at_soap.pipex.net>...Received on Thu Mar 15 2001 - 18:20:48 CET
>> You certainly should not be able to
>> enable or disable a trigger in the
>> middle of a transaction - if that's
>> what you meant - as the command:
>>
>> alter trigger xxx disable;
>>
>> will issue an implicit commit, and
>> end the current transaction.
>
>No, my question was about enabling or disabling
>trigger from third session.
>
>WBR, Alexander
>
>
>
