#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: dev
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 Tim Graham):
Leaving database defaults would be backward incompatible and could result
in surprising behavior. `Field.default` can be a callable which returns a
non-static value that could be inappropriate as a long-running default.
#470 is a new feature ticket to allow using database defaults.
--
Ticket URL: <https://code.djangoproject.com/ticket/28000#comment:16>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183c8b2d8c0-2080eeb1-24a0-4621-adf9-aefd760d3e94-000000%40eu-central-1.amazonses.com.
