List:Internals« Previous MessageNext Message »
From:Vasil Dimov Date:January 3 2008 7:23am
Subject:Re: MySQL uses PRIMARY key when it should? use another index
View as plain text  
On Wed, Jan 02, 2008 at 07:15:24 -0800, Rick James wrote:
> I would be surprised if using t1ba is ever the 'right' way to do the
> query.  The "(10)" virtually destroys any usefullness of the index.  And
> since you asked for "a,b", it could really be satisfied in the index.  I
> do find it puzzling that it says both "PRIMARY" and "Using index".
[...]

Well, I am not asserting that using t1ba is "right" or "better" than
using the primary key; or the other way around.

I observed a change in behavior and am trying to find the changeset that
caused it. If the comment says something like "Fix uppercase letters"
then the change in behavior is some side effect and is probably not
intended. If it is "Improve index handling or whatever" then it is
probably intended...

-- 
Vasil Dimov
moc.elcaro@stripped        Software Developer @ Oracle/Innobase Oy
gro.DSBeerF@dv                Committer @ FreeBSD.org
gro.d5v@dv                    Home @ Sofia, Bulgaria

Attachment: [application/pgp-signature]
Thread
MySQL uses PRIMARY key when it should? use another indexVasil Dimov2 Jan
  • RE: MySQL uses PRIMARY key when it should? use another indexRick James2 Jan
    • Re: MySQL uses PRIMARY key when it should? use another indexVasil Dimov3 Jan
    • Re: MySQL uses PRIMARY key when it should? use another indexMarko Mäkelä3 Jan
      • Re: MySQL uses PRIMARY key when it should? use another indexMarko Mäkelä3 Jan
  • Re: MySQL uses PRIMARY key when it should? use another indexJoerg Bruehe4 Jan
  • Re: MySQL uses PRIMARY key when it should? use another indexSergei Golubchik4 Jan