#23581: Migration shouldn't generate "DROP DEFAULT" SQL if no database changes
are
required
-------------------------------------+-------------------------------------
Reporter: john_scott | Owner: timgraham
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"a9da5dd5b6f722a230a69211ad8e00a20cafcd38"]:
{{{
#!CommitTicketReference repository=""
revision="a9da5dd5b6f722a230a69211ad8e00a20cafcd38"
[1.7.x] Fixed #23581 -- Prevented extraneous DROP DEFAULT statements.
Thanks john_scott for the report and Markus Holtermann for review.
Backport of ab4f709da4516672b0bd811f2b4d0c4ba9f5b636 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23581#comment:26>
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.e565fab4c14f008e1b6af160052f364e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
