SQL Simultaneous transactions ignore each other's locks??? DEADLOCK [InnoDB, Python]
问题 Good day! I've run into a head burner. My client requires me to repurpose a python program to work with MySQL instead of Microsoft's SQL Server. I'm having trouble finding an equivalent solution in SQL. I can't seem to create a proper update lock on a row. When two identical transactions execute simultaneously, they both read the row despite opening a transaction at the serialize isolation level, and with SELECT ... FOR UPDATE. Maybe my code will explain it better: execute("SET TRANSACTION