Use indexes. Make sure your indexes are on the right side of the where
clause ie.
SELECT col1,col2 from tablewithproperindexes where col3=const_index_lookup.
Or you can use a dirty read as your transaction model to help out a TINY
bit.
--
DVP
> -Original Message-
> From: [EMAIL PROTECT
It would appear that MySql does table locking. Then I would like to ask
the
following:
> From what I've read,
> it would seem that SELECTS get a lower priority than INSERTS and UPDATES,
> meaning that if all 30 users
> insert into that table at the same time (given the way the stress test is
>
On Mon, Feb 17, 2003 at 11:22:27AM +0200, Rob wrote:
> Thanks
>
> It would appear that MySql does table locking. Then I would like to
> ask the following:
Hi Rob,
I think that you missed some important details.
Taken from the manual:
"MySQL only supports table locking for ISAM/MyISAM
e RSA
Smart Business Innovation
http://www.jamwarehouse.com
**
-Original Message-
From: Zak Greant [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 11:10 AM
To: Rob
Cc: [EMAIL PROTECTED]
Subject: Re: Mysql Table locking
On Mon, Feb 17, 2003 at 11:00:37AM +0200,
> Can I just check, does MySql v.3.23.52 do table locking or row locking?
If
> it only does table locking, are there any versions of mysql that do row
> locking?
Always Read The Fine Manual:
>From http://www.mysql.com/doc/en/Locking_methods.html:
"Currently MySQL only supports table locking fo
On Mon, Feb 17, 2003 at 11:00:37AM +0200, Rob wrote:
> Hi all,
>
> Can I just check, does MySql v.3.23.52 do table locking or row locking? If
> it only does table locking, are there any versions of mysql that do row
> locking?
Detailed in the fine manual:
http://www.mysql.com/search/index.ph
