Hi Robert,
On Tue, Apr 1, 2008 at 1:01 PM, Robert DiFalco <[EMAIL PROTECTED]> wrote:
> I've been told that an index always contains the primary key. So if I
A non-primary key index, in InnoDB, contains the primary key values at
the leaf nodes. However it does not contain them at the non-leaf
nod
Hi !
Robert DiFalco wrote:
Right, the proof is that if I have an PKEY on ID and an index just on
VALUE in MySQL then a query that would use both ID and VALUE works fine
with just the index on VALUE.
An index is a means to speed up access to the data when the most
identifying thing, the primar
Right, the proof is that if I have an PKEY on ID and an index just on
VALUE in MySQL then a query that would use both ID and VALUE works fine
with just the index on VALUE.
For Oracle, I need an explicit compound index (in addition to the PKEY)
on (ID,VALUE).
The results on MySQL get a little blur
There is already a primary key index on ID.
-Original Message-
From: Wm Mussatto [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2008 10:50 AM
To: mysql@lists.mysql.com
Subject: Re: Indices in InnoDB/MySQL
On Tue, April 1, 2008 10:01, Robert DiFalco wrote:
> I've been told
At 10:01 AM -0700 4/1/08, Robert DiFalco wrote:
I've been told that an index always contains the primary key.
By who?
Ask for proof.
So if I
have a LONG ID that is the primary key of table and create on index on
LONG VALUE, the index on LONG VALUE will actually work as a typical
compound i
On Tue, April 1, 2008 10:01, Robert DiFalco wrote:
> I've been told that an index always contains the primary key. So if I
> have a LONG ID that is the primary key of table and create on index on
> LONG VALUE, the index on LONG VALUE will actually work as a typical
> compound index on ID,VALUE. My
