-
From: Dwight Altman [EMAIL PROTECTED]
To: php-db@lists.php.net
Sent: Wednesday, August 10, 2005 4:23 PM
Subject: [PHP-DB] SELECT Performance and INDEXing
I have a MyISAM table holding images with field types bigint(20),
mediumblob, varchar(255), blob and tinyint(3). The table has grown
[EMAIL PROTECTED]
To: php-db@lists.php.net
Sent: Wednesday, August 10, 2005 4:23 PM
Subject: [PHP-DB] SELECT Performance and INDEXing
I have a MyISAM table holding images with field types bigint(20),
mediumblob, varchar(255), blob and tinyint(3). The table has grown to
over
800 MB
[EMAIL PROTECTED]
To: php-db@lists.php.net
Sent: Thursday, August 18, 2005 9:49 AM
Subject: Re: [PHP-DB] SELECT Performance and INDEXing
I think no one answered it because it doesn't make a whole lot of sense.
Breaking a condition out into a second SQL statement would force the DB to
rescan
Subject: Re: [PHP-DB] SELECT Performance and INDEXing
I think no one answered it because it doesn't make a whole lot of sense.
Breaking a condition out into a second SQL statement would force the DB
to rescan the table, so it should take longer rather than shorter.
There's nothing suggesting
Message -
From: Dwight Altman [EMAIL PROTECTED]
To: php-db@lists.php.net
Sent: Wednesday, August 10, 2005 4:23 PM
Subject: [PHP-DB] SELECT Performance and INDEXing
I have a MyISAM table holding images with field types bigint(20),
mediumblob, varchar(255), blob and tinyint(3
I have a MyISAM table holding images with field types bigint(20), mediumblob,
varchar(255), blob and tinyint(3). The table has grown to over 800 MB and over
6,000 rows. In the past week, performance has been about 15-20 seconds to run
the following select statement which pulls only 16 maximum
I meant
'Analyze table'
and
'the composite key field2 field3 would be unique'
- Original Message -
From: Dwight Altman [EMAIL PROTECTED]
To: php-db@lists.php.net
Sent: Wednesday, August 10, 2005 4:23 PM
Subject: [PHP-DB] SELECT Performance and INDEXing
I have a MyISAM table holding