#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 andrewgodwin):
So: excessive DROP DEFAULT is a valid issue, and what this ticket should
represent.
Issuing a field alter on every change is by design (as tim said above) and
we can't go back on that - due to the way state building works we need to
have every attribute change represented that might affect the database OR
data migrations - and things like choices and especially defaults matter
in database migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/23581#comment:9>
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.7aeecca34117755b33795dd4d6b5419f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
