MyISAM can't do this but innodb can. If you change to an innodb table and define your index as the primary key then row data is clustered with the primary key. This means there is no additional storage overhead for the primary key because it is just the row data. This will break down if you define secondary indexes though because the primary key is copied for each secondary index.
http://dev.mysql.com/doc/refman/5.0/en/innodb-index-types.html On Sat, Nov 24, 2012 at 1:15 PM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 24.11.2012 22:02, schrieb Hank: >> Hello everyone, >> >> I know this is a longshot, but is there any way to eliminate the MYD >> file for a table that has a full covering index? The index is larger >> than the datafile, since it contains all the records in the datafile, >> plus a second reverse index. It seems redundant to have to also store >> a MYD file > > simple answer: NO > -- Eric Bergen eric.ber...@gmail.com http://www.ebergen.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
