#1407: Regression: enum are VARCHAR in MySQL
-------------------------+--------------------------------------------------
Reporter: colnector | Owner: jwage
Type: defect | Status: closed
Priority: critical | Milestone: New
Component: Attributes | Version: 1.0
Resolution: wontfix | Keywords:
Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 0 |
-------------------------+--------------------------------------------------
Changes (by romanb):
* status: new => closed
* resolution: => wontfix
Comment:
http://trac.doctrine-project.org/changeset/4768
Emulated enums with integer conversion caused nothing but trouble so we
pulled the emergency break. If you want "emulated" enums, these are now
stored as varchar, yes. Set a proper maximum size for the varchar. More
bytes, more readable database. If you dont want to "waste" bytes use
native enums (USE_NATIVE_ENUMS = true). Or even pull the enum in a
separate table ("full normalization").
"Emulated" enums that store integer values are gone forever.
--
Ticket URL: <http://trac.doctrine-project.org/ticket/1407#comment:2>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
