Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of deeky666:
SQL Server implements column default values as constraints and therefore requires them to be dropped before a column type change.
This PR implements the recreation of default constraints on column type alterations.
Additionally some code in SQLServerPlatform::getAlterTableSQL() has been refactored to avoid code duplication and unnecessary SQL generation.
Please note that due to the issue's tests the PostgreSQL platform had to be altered to fulfill the same behaviour. PostgreSQL returned some strange default value like 666:smallint when reverse engineering a column type change with a default value of 666 from type smallint to integer. So I think this PR fixes a bug in this platform, too. Additionally I had to change the deprecated default value retrieval SQL in PostgreSQL in order to work flawlessly. See the documentation at the very end.
I would also like to note that this PR is definitely not the end of the line concerning default values and column alterations. Some weird errors were revealed on other platforms while fixing this issue. MySQL for example denies default values on BLOB/TEXT type columns, DB2 just throws non-understandable syntax errors around and Oracle seems to map decimal/numeric types without a defined scale to integer when reverse engineering (not really related to this issue but it came up while testing).
Otherwise the tests pass on all platforms.
Comment created by @doctrinebot:
A related Github Pull-Request [GH-536] was closed:
A related Github Pull-Request [GH-542] was closed:
Comment created by @deeky666:
Fixed in commit: 171a876
Issue was closed with resolution "Duplicate"