#28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null
-------------------------------------+-------------------------------------
Reporter: Matteo Pietro Russo | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution: duplicate
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 Marcin Nowak):
> Django's ORM don't use defaults defined at the database level
But it should.
--
Ticket URL: <https://code.djangoproject.com/ticket/28000#comment:14>
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/065.429dcf2512678e5c85d541098be39449%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
