----- 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, 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 have more lock contention at
> a higher isolation level.
>
> Jeremy
Yes, you can't have it both ways...If you use SERIALIZABLE on one
transaction, it will affect other transactions operating on the same data.
REPEATABLE_READ will not buy you much if it's working on the same data as
transactions running at the SERIALIZABLE isolation level.
Use SERIALIZABLE isolation levels with care, and only when you need
to....and count on deadlocks...That's true with any database. Your
application logic (unless very carefully crafted) will be creating the
deadlocks, not the database itself.
-Mark
--
~ __ ___ ___ ____ __
~ / |/ /_ __/ __/ __ \/ / Mark Matthews <[EMAIL PROTECTED]>
~ / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer - JDBC/Java
~ /_/ /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA
~ <___/ www.mysql.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
