#27928: Avoid SET/DROP DEFAULT unless a field changes from null to non-null
-------------------------------------+-------------------------------------
Reporter: Christophe Pettus | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Migrations | Version: master
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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* owner: Christophe Pettus => Simon Charette
* version: 1.10 => master
Comment:
I'll reuse #28000's summary which was closed as duplicate as it exemplify
the general issue more appropriately.
In the subcase reported here setting `blank=True` changes the effective
default for operations adding/altering non-nullable fields which trigger
the actual bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/27928#comment:6>
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.4b4b45f5135d94ec169727a21c266d68%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
