Hello All
V4.0.16 on Sun Sparc 5.8
Innodb_lock_wait_timeout = 50.
A application using jboss got this error a few days ago. The SQL being used, AFAIK,
was a simple delete from table where date = {date}.
I am trying to determine why this happened. Searching back in the MySQL lists
archives, I
General (E-mail)
Subject: Innodb Message Lock wait timeout exceeded; Try restarting
transaction
Hello All
V4.0.16 on Sun Sparc 5.8
Innodb_lock_wait_timeout = 50.
A application using jboss got this error a few days ago. The SQL being
used, AFAIK, was a simple delete from table where date
when it happened
originally.
-Original Message-
From: Dathan Vance Pattishall [mailto:[EMAIL PROTECTED]
Sent: Monday, September 13, 2004 2:49 PM
To: Tucker, Gabriel; 'Mysql General (E-mail)'
Subject: RE: Innodb Message Lock wait timeout exceeded; Try restarting
transaction
Basically
Hi. I have a question about rollbacks and innodb.
Suppose that a query begins with begin. Then a couple inserts happen but
before the commit statement is executed, the client hits stop in the
browser. What is going to do the rollback? If there is a persistent
connection, is it going to wait for
and lock wait timeout
Hi. I have a question about rollbacks and innodb.
Suppose that a query begins with begin. Then a couple inserts happen but
before the commit statement is executed, the client hits stop in the
browser. What is going to do the rollback? If there is a persistent
connection
Hi,
On Sat, Apr 06, 2002 at 03:57:39PM -0500, Victor wrote:
Suppose that a query begins with begin. Then a couple inserts happen but
before the commit statement is executed, the client hits stop in the
browser. What is going to do the rollback? If there is a persistent
connection, is it
