key, so I
was wondering if some type of composite index on (field2, field3) would be
better. Then again, any combination with field1 would also be unique.
- Original Message -
From: "Micah Stevens" <[EMAIL PROTECTED]>
To:
Sent: Thursday, August 18, 2005 12:33 PM
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
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 that it's doing an internal self-join or other
time-con
Hey, this is my first question. So if you could just reply to say it
reached the php-db list, that would be terrific. Of course, answering the
questions would be awesome as well.
> I meant
> 'Analyze table'
> and
> 'the composite key "field2 field3" would be unique'
>
> - Original Message --
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 INDEXing
I have a MyISAM table holding images with fiel
