Enums

[Shane H. W. Travis]

> On Tue, 1 Feb 2005, Gervase Markham wrote:
> > There may, of course, be some reason (like "we have to get rid of enums
> > ASAP for PostGres support") why that wouldn't work...

AIUI ENUMs are MySQL-specific, and don't port well across databases... so
what you mention is definitely one reason.


On Tue, 1 Feb 2005, Kevin Benton wrote:
> At this point, there is no guarantee that a custom fields patch will land
> prior to the 2.20 freeze, but there's a really good chance that the
> conversion of enums will.

This is another really good reason. If you've already got one bird in the
hand, then you only need ONE of those two from that bush over there...

Also, Gerv, I think you're mistaking 'discussion' for 'movement' on Custom
Fields. Right now there's a proposal (and a patch) on the table that appears
to be unacceptable to several people. If that gets shot down, we're right
back where we started; nowhere.

If the ENUMS patch is ready to go, then don't hold it up in favour of some
future developments that may or may not come to pass.

Shane H.W. Travis       | The greatest of all mistakes is to do nothing
travis at sedsystems.ca    |  because you can only do a little.
Saskatoon, Saskatchewan |   Do what you can.  -- Sydney Smith