Re: Mix betwenn storage procedures and transactions
Posted by: Rick James
Date: April 30, 2014 10:57AM

What you have done (START+COMMIT) is no different than using autocommit.

Your UPDATEs are hitting every row? How big are the tables?

What does fn_update() do?

I am fishing for whether this Procedure is destined to take a long time (lots of rows + slow function), or whether some optimization/simplification can be made.

If it turns out that you need to do the UPDATEs piecemeal, see this for a discussion of chunking the action (it talks about DELETE, but can be adapted to UPDATE): http://mysql.rjweb.org/doc.php/deletebig

Options: ReplyQuote


Subject
Written By
Posted
Re: Mix betwenn storage procedures and transactions
April 30, 2014 10:57AM


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.