Is there any chance of this changing in a future release? I mean, for a data type that can supposedly support 65535 different enumerated values, having a key space of only 65536 bytes seems inappropriate. So, I guess I could have that many, only if each entry was one byte of text. That seems pretty much useless to me.

Is it possible to change this and recompile? Or is it likely to fundamentally break something? I would really like to use ENUMs for our DB, but as they are currently implemented, they are pretty useless. I don't see why there really needs to be a limit here, as I can implement the same functionality with look-up tables. It's just nice if I don't have to, by having it built into the system.

I wouldn't mind the DB getting a lot bigger by declaring, say, 1MB for string storage for each column. It's better than increasing it by a factor of 16 to 32 times, by using 64 bytes of char instead of 2 bytes of enum for each cell.

For now, I guess we will be implementing our own 'enum' types by using look-up tables for each column.