- Original Message -
From: "Jeremy Zawodny" <[EMAIL PROTECTED]>
To: "Joe Shear" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 09, 2002 5:27 PM
Subject: Re: InnoDB Locking Problems
> On Fri, Aug 09, 2002 at 02:38:03PM -0700,
yes, we are running at serializable, which also explains the locking
problems, especially since we just upgraded from .49.
thanks
joe
On Fri, 2002-08-09 at 15:27, Jeremy Zawodny wrote:
> On Fri, Aug 09, 2002 at 02:38:03PM -0700, Joe Shear wrote:
>
> [snip]
>
> > COMMIT
> > we are using the high
On Fri, Aug 09, 2002 at 02:38:03PM -0700, Joe Shear wrote:
[snip]
> COMMIT
> we are using the highest level of transactional security -- the term for
> it eludes me at the moment.
You mean the isolation level? Are you running at SERIALIZABLE rather
than READ-COMMITTED? IF so, why? You will h
I'm using mysql 3.23.51 w/ InnoDB tables, and am running into some
locking issues which I don't believe should occur. There are 2
transactions that seem to interfere with each other. The first
transaction is an update of one table followed by a select of another
table, ie:
BEGIN
UPDATE table1 se
