[DBAL-504] DBAL Enum fields migration issue / PostgreSQL Created: 24/Apr/13 Updated: 06/May/13
|Component/s:||Drivers, Schema Managers|
|Reporter:||jos de witte||Assignee:||Benjamin Eberlei|
When using Custom Doctrine DBAL Enums the migration created using diff
works fine the first time.
However the next time it generates a SQL statement trying to change to field type to INT from integer; (Redundant)
"ALTER schemaname.fieldname SET" .. And that's it.
|Comment by Tom Vogt [ 01/May/13 ]|
Doesn't only happen on Enums. I don't use any enums and I have this problem. I use a couple of geo (postGIS) fields (point, linestring, polygon) as well as array fields, so either or all of those might be causing it, too.
|Comment by Benjamin Eberlei [ 04/May/13 ]|
We did some changes for PostgreSQL column diffs lately, can you verify this bug still exists on the 2.3 Branch of DBAL?
|Comment by Tom Vogt [ 06/May/13 ]|
I'm running this on Symfony2 with this composer.json config:
and I'm still getting this issue today.