MSSQL is fat & ugly and cannot drop column if default value is set. I’ve tried to fix this by creating custom DropColumnChange implementation which generates additional DropDefaultValueStatement, but this fails for another reason: dropping non-existing constraint causes crash. So…
a) this is not an issue, you must always directly drop default value (stupid?)
b) this is an issue, should be solved this way, and dropDefaultValues should be a NOP if no constraint present (easy?)
c) this is an issue and should be solved another way (most elegant?)
d) other (?)
What do you think about this?