DBAL-4: missing column type "enum" about dbal

[doctrinebot]

• depends on DBAL-1116: [GH-774] Added SET and ENUM types for MySQL and fix issue with schema update tool
• is referenced by DBAL-89: MySqlPlatform does not handle enum and set data types
• is referenced by DBAL-504: DBAL Enum fields migration issue / PostgreSQL
• is referenced by DDC-2469: SQLite handling for ENUM-Fields

[doctrinebot]

Comment created by romanb:

D2 has no enum type (because php has no enum type), we might need a new type class for this if necessary. Might be non-trivial.

[doctrinebot]

Comment created by chriswest:

Yes, a new type class is needed. It should be possible (like in D1) to configure the list of available enum elements.

example from D1 doc:

---
Test:
  columns:
    enumtest:
      type: enum
      values: [php, java, python]

Would be important regarding migration issues.

[doctrinebot]

Comment created by shurakai:

Roman, is your response to be considered a "we will work on this" or a "probably won't implement it". I'm asking because I was thinking whether I should get into this or not.

[doctrinebot]

Comment created by @beberlei:

My take, given the flyweight architecture of our type-system this is only implementable with a specific Enum class in the userland. The only thing we could offer would be an abstract class to extend from. This would rather be a task for a Doctrine Extension in my opinion, or even a documentation/cookbook problem.

[doctrinebot]

Comment created by @hobodave:

I see this as a non-issue. It belongs in an extension. ENUM is specific to MySQL, and is one of the most misused columns.

[doctrinebot]

Comment created by @beberlei:

Change to minor

[doctrinebot]

Comment created by @beberlei:

See http://www.doctrine-project.org/docs/orm/2.0/en/cookbook/mysql-enums.html

That is everything we can provide.

[doctrinebot]

Issue was closed with resolution "Won't Fix"

[doctrinebot]

Imported 1 attachments from Jira into https://gist.github.com/350350cd1020e4519192

• 10122_enum_type_patch.patch

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.