MySQL :: Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

New Topic

Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

Posted by: David Hernandez
Date: April 27, 2021 07:48PM

Peter, I do appreciate the answer. If it is not too much to ask, would you please send me a link to the particular subject explained in your reply. The reason for the asking if because I have looked and looked for it to no avail. I cannot locate that particular material that relates to your answer. Again, thank you. Newby D. Hernandez

Navigate: Previous Message• Next Message

Options: Reply• Quote

Subject

Views

Written By

Posted

Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

2378

David Hernandez

April 24, 2021 04:26PM

Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

1032

Peter Brawley

April 24, 2021 07:04PM

Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

1316

David Hernandez

April 26, 2021 07:33PM

Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

3334

Peter Brawley

April 27, 2021 10:32AM

Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

1576

David Hernandez

April 27, 2021 07:48PM

Re: Error Code: 1442. Can't update table tablename in stored function/trigger because it is already used by statement which invoked this stored function

985

Peter Brawley

April 27, 2021 08:24PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.