 | |
Mutating table with old and new ... only
comp.databases.oracle.misc comp.databases.oracle.misc
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Mutating table with old and new ... only -
08-27-2008
, 02:07 PM
#2
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin :new.ROW :=  ld.ROW;.... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
Go to Morgan's Library at www.psoug.org and click on
Table Triggers.
Run the demo that creates the error to learn what creates
it and how to avoid it.
Essentially what must happen to create the error is that
the trigger must query the table on which DML is being
performed.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
#3
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin :new.ROW := ld.ROW;.... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
Go to Morgan's Library at www.psoug.org and click on
Table Triggers.
Run the demo that creates the error to learn what creates
it and how to avoid it.
Essentially what must happen to create the error is that
the trigger must query the table on which DML is being
performed.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
#4
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin :new.ROW := ld.ROW;.... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
Go to Morgan's Library at www.psoug.org and click on
Table Triggers.
Run the demo that creates the error to learn what creates
it and how to avoid it.
Essentially what must happen to create the error is that
the trigger must query the table on which DML is being
performed.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
#5
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin :new.ROW := ld.ROW;.... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
Go to Morgan's Library at www.psoug.org and click on
Table Triggers.
Run the demo that creates the error to learn what creates
it and how to avoid it.
Essentially what must happen to create the error is that
the trigger must query the table on which DML is being
performed.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
#6
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin * :new.ROW := ld.ROW;* .... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
constraint or if someone else is updating the table. See
http://asktom.oracle.com/tkyte/Mutate/index.html (which refers to the
docs http://download-west.oracle.com/docs...g13trg.htm#786
) and search on the term mutating at asktom.oracle.com for the many
variants of this.
You have to remember when you try things out to try the things that
will cause the problem. This can be more difficult than some people
expect, given a complicated system.
jg
--
@home.com is bogus.
Wormmmmmsss innnnn Spaaaaaaacccce. http://news.bbc.co.uk/1/hi/technology/7583805.stm
#7
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin * :new.ROW := ld.ROW;* .... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
constraint or if someone else is updating the table. See
http://asktom.oracle.com/tkyte/Mutate/index.html (which refers to the
docs http://download-west.oracle.com/docs...g13trg.htm#786
) and search on the term mutating at asktom.oracle.com for the many
variants of this.
You have to remember when you try things out to try the things that
will cause the problem. This can be more difficult than some people
expect, given a complicated system.
jg
--
@home.com is bogus.
Wormmmmmsss innnnn Spaaaaaaacccce. http://news.bbc.co.uk/1/hi/technology/7583805.stm
#8
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin * :new.ROW := ld.ROW;* .... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
constraint or if someone else is updating the table. See
http://asktom.oracle.com/tkyte/Mutate/index.html (which refers to the
docs http://download-west.oracle.com/docs...g13trg.htm#786
) and search on the term mutating at asktom.oracle.com for the many
variants of this.
You have to remember when you try things out to try the things that
will cause the problem. This can be more difficult than some people
expect, given a complicated system.
jg
--
@home.com is bogus.
Wormmmmmsss innnnn Spaaaaaaacccce. http://news.bbc.co.uk/1/hi/technology/7583805.stm
#9
| |||
| |||
|
|
Hello, I have been told that something like: create trigger triggername before update of ROW on TABLE for each row when (old.ROW = a and new.ROW = b) begin * :new.ROW := ld.ROW;* .... message "a could not be updated with b" end; / would cause the mutating table error. Certainly I have tried it out and did not receive this error. From my knowledge new and old are just "copies" and since I am not accessing the table/row which is going to be updated/or not an mutating error could not happen in this context, right? In general I wonder if the trigger above could be used or if it is better to have such logic somewhere else? Thanks much in advance for you help. Best regards, Dirk. |
constraint or if someone else is updating the table. See
http://asktom.oracle.com/tkyte/Mutate/index.html (which refers to the
docs http://download-west.oracle.com/docs...g13trg.htm#786
) and search on the term mutating at asktom.oracle.com for the many
variants of this.
You have to remember when you try things out to try the things that
will cause the problem. This can be more difficult than some people
expect, given a complicated system.
jg
--
@home.com is bogus.
Wormmmmmsss innnnn Spaaaaaaacccce. http://news.bbc.co.uk/1/hi/technology/7583805.stm
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.