Enumerate and remove DEFAULT constraints #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SQL Server implements in-database DEFAULT conditions as constraints, and requires that they be explicitly dropped before allowing the related column to be removed. Extend introspection to detect these constraints and return them as a new constraint type. Make the schema editor read and remove these constraints when removing a column.
Django doesn't generally use in-database DEFAULTs, but they can exist in legacy databases other tools have touched. For example: old versions of South would accidentally leave defaults in place after a migration to make a nullable column non-nullable. This can cause unexpected migration failures trying to delete the column later on.