Re: MySQL 8.0 Command Line Client Error 1205
That script has issues, eg DDL cmds cause implicit commits, "close transaction" does not exist as a MySQL cmd. And the commit cmd in this script ends the transaction, so it can't cause a deadlock. I'm unable to replicate your reported deadlock using the code you've posted.
If the script is corrected and the commit is commented out, of course a second session trying to update the same row with have to wait till the first transaction locks are released. Did you read the suggested article?
> I will start using the InnoDB section for miscellaneous
> MySQL Command Line issues from now on.
It's an InnoDB issue, not a commandline issue.
Subject
Views
Written By
Posted
869
July 17, 2022 03:20PM
587
July 17, 2022 03:57PM
487
July 17, 2022 05:45PM
Re: MySQL 8.0 Command Line Client Error 1205
517
July 17, 2022 08:29PM
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.