#27928: Avoid SET/DROP DEFAULT unless a field changes from null to non-null
-------------------------------------+-------------------------------------
Reporter: Christophe Pettus | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"35c0025151ad411e691a2fa62a0dd3507ebafd82" 35c0025]:
{{{
#!CommitTicketReference repository=""
revision="35c0025151ad411e691a2fa62a0dd3507ebafd82"
Fixed #27928 -- Avoided SET/DROP DEFAULT unless a field changes from null
to non-null.
Thanks Christophe Pettus, Matteo Pietro Russo for reports and Tim for
review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27928#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/061.9e7f5db43134c1cdc6e7874133336380%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
