Robert,
----- Original Message ----- From: ""Bagyinszki Róbert"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, October 26, 2004 12:46 PM
Subject: deadlock caused by odbc and transaction handling
------_=_NextPart_001_01C4BB40.B000D6DB Content-Type: text/plain; charset="iso-8859-1"
We are making a multithreaded application on a Solaris 8 system, with mysql
3.23 - InnoDB tables, myodbc 3.51.06, unixODBC2.2.10. When 2 threads want to
update a record of a table at the same time, a deadlock is occured. One of
them is waiting for the end of the transaction of the other thread - this is
normal. But the other thread is waiting in an ODBC method, like SQLRowCount,
or SQLAllocHandle. Only when the transaction is ended with timeout in first
thread, can it continue.
Is this a known problem, or maybe we misuse some function?
I assume that you are using two DIFFERENT connections for the threads? That is the correct way.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php
Order MySQL technical support from https://order.mysql.com/
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
