Comments
|
Posted By preethi On 17-Jun-10 07:50:11 AM
thanks for providing solution for mutating problem,sir..It is very helpful
|
|
Posted By ravikumar On 05-Aug-11 01:31:17 AM
gud one
|
|
Posted By Raaj On 26-Oct-12 09:05:07 AM
Article is nice.
|
|
Posted By JW On 14-May-13 04:01:34 AM
Very clever, But writing 3 triggers to get around a design flaw is not the answer. Create a stored procedure that checks the data before the update.
|
|
Posted By SG On 01-Feb-14 03:21:36 PM
think, intead of these three triggers we can get rid off this using a compound trigger or at least using a statement level trigger
|
|
Posted By Shubham On 12-Feb-14 04:29:03 PM
Good explanation sir
|
|
Posted By Shubham On 12-Feb-14 04:35:55 PM
How can we define the execution order of these triggers?
|
|
Posted By Manjunath On 18-Aug-15 04:00:14 PM
Cau you please tell me how to avoid mutating trigger error while we update triggering table.
|
|
Posted By Girish On 03-Mar-16 01:38:23 PM
Pretty smart idea. Kudos to the author!
JW, Stored proc has to be explicitly called every time to check it. Whereas trigger automatically fires to ensure data integrity.
Shubham, From Oracle 11g onwards, you can use FOLLOWS trigger_name to make sure the order of triggers.
Manjunath, Answer to your query is this article itself!
|
|
Posted By Dashasr On 19-Feb-17 05:13:34 AM
???????????! ????????? ??? ???????? ???????? ?? ???????? ?? ????: ?????? ? ????????? ??? ??????
??? ???????? ????, ??? ????? ?????????? ? ????????? ?????? ???????? ?? ???? ??? ??? ? ???????, ?????????? - ??????????. ??? ????? ??? ???? ?????? ????????? ??????.
?????????? ?? ?????? ???? ? ??????? ??? ???????????
?????????? ?????? fas.st/VPUID
|