terrific. Of course, answering
>> the
>> questions would be awesome as well.
>>
>> > I meant
>> > 'Analyze table'
>> > and
>> > 'the composite key "field2 field3" would be unique'
>> >
>> > - Orig
ld2 9 const 10 Using where; Using
> filesort
>
>
> ----- Original Message -
> From: "Micah Stevens" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, August 18, 2005 9:49 AM
> Subject: Re: [PHP-DB] SELECT Performance and INDEXing
>
> > I think no
evens" <[EMAIL PROTECTED]>
To:
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 th
ey "field2 field3" would be unique'
> >
> > - Original Message -
> > From: "Dwight Altman" <[EMAIL PROTECTED]>
> > To:
> > Sent: Wednesday, August 10, 2005 4:23 PM
> > Subject: [PHP-DB] SELECT Performance and INDEXing
> >
> >
be unique'
>
> - Original Message -
> From: "Dwight Altman" <[EMAIL PROTECTED]>
> To:
> 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
I meant
'Analyze table'
and
'the composite key "field2 field3" would be unique'
- Original Message -
From: "Dwight Altman" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, August 10, 2005 4:23 PM
Subject: [PHP-DB] SELECT Performance and INDEXi
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
