Re: innodb deadlock on UPDATE

[Rick James]

> I want to keep things simple.

"Simple" instead of "correct"? For example:

BEGIN;
$ct = SELECT `count` FROM table WHERE ...; -- Without FOR UPDATE
...
UPDATE table SET `count` = $ct+1;
COMMIT;

During the "..." a different transaction could increment `count`, thereby messing up the UPDATE.

Sure, doing "SET count = count + 1" might be a solution. But not if the `count` from the SELECT is used to decide whether or not to do the UPDATE.

> thousands witin each transaction

This may not be wise. Can it be broken into smaller "transactions" and still provide the desired integrity?