Re: Using an ENUM column in an index

[Tom Byars]

Thanks for the reply Peter. The enum field will be the last column in five different indexes and will have 255 possible values. The table has around 2.5 million rows and rising.

The alternative to the enum column is two columns that require a total of 4 bytes so using the enum would save me 7.5 MB per index (37.5 MB in total) assuming the enum column will only take up one byte per entry in the index.