#23581: Migration shouldn't generate "DROP DEFAULT" SQL if no database changes
are
required
--------------------------------------+------------------------------------
Reporter: john_scott | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by john_scott):
The `DROP DEFAULT` is due to ticket #23043. In
@5875b8d13333bf709b54f91a143304826d57f2fd a bit of code was added so that
any time DatabaseSchemaEditor._alter_field() is called it will always add
`DROP DEFAULT` even when there is no default to drop.
--
Ticket URL: <https://code.djangoproject.com/ticket/23581#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.ef7caa1405e68f433d3130d7bbdbe9fc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
