Comment 3 for bug 660038
Revision history for this message
| Stewart Smith (stewart) wrote Re: [Bug 660038] [NEW] Add CREATE TABLE option to force InnoDB to use a short 6 byte internal key | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
On Wed, 13 Oct 2010 20:14:20 -0000, Swany <email address hidden> wrote:
> Summary tables in particular have this problem. A summary table may
> have a very long (in terms of bytes) unique key or primary key, but
> this causes a huge problem for secondary keys.
Only if you want to get at columns not in the primary key.
Using the pkey for the value in secondary indexes does let you get other
pkey values without getting the main record. This of course may/may not
be what you want.
> In this case, I want this table to have an internally clustered key.
> The tables are maintained by software, and it doesn't make sense to
> maintain auto_increment values on a summary table. That is ugly and
> not efficient.
This may not be too hard to add as an option.... but I'd only want to be
adding it to HailDB, not the innobase plugin.
--
Stewart Smith