Daniel Cummings wrote:
We want to convert a 200+ meg table to a heap table. We've gotten pretty
good performance converting from InnoDb to MyIsam table but converting to a
heap table would give an even bigger performance boost.
You think it would, or it already has in your testing? Heap vs. MyISAM
You can't do efficient ranging on a HASH indexed column without a table
scan...
Select * from heap_table where indx_col between 247 and 258
This would table scan your 200meg table even if "indx_col" is a PRIMARY
KEY, using the default hash key. Hash key was the only choice prior to
4.1, but now y
