Gleb Paharenko wrote:
Hello.
Among other things check that you correctly process lock timeouts.
I've check this, but it seems fine.
I'm testing it this way with 3 applications on the same computer (2
processors) :
- 2 clients applications with an open connection to the DB (which is
remote with
while i can insert with the other
one, then the SELECT .. FOR UPDATE returns with the first
mysqlclient), but with my applications, I sometimes get an error 1213
(DEADLOCK) from innodb. The documentation state that the transaction
should be rerun. If I do it, it works fine. What does cause
Hello.
Among other things check that you correctly process lock timeouts.
Well, I'm sure it's a bug hidden somewhere in my apps, i've check with
another connexion and it worked ;)
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is
get an error 1213 (DEADLOCK) from innodb.
The documentation state that the transaction should be rerun. If I do
it, it works fine. What does cause this deadlock ?
If I trace my queries I could see the inserts going _twice_ and one does
fails on this deadlock. I don't really understand why
sometimes get an error 1213 (DEADLOCK) from innodb.
The documentation state that the transaction should be rerun. If I do
it, it works fine. What does cause this deadlock ?
If I trace my queries I could see the inserts going _twice_ and one does
fails on this deadlock. I don't really understand why
applications, I sometimes get an error 1213 (DEADLOCK) from innodb.
The documentation state that the transaction should be rerun. If I do
it, it works fine. What does cause this deadlock ?
If I trace my queries I could see the inserts going _twice_ and one does
fails on this deadlock. I don't
