#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 Alessio Fachechi):
Replying to [comment:14 Marcin Nowak]:
> > Django's ORM don't use defaults defined at the database level
>
> But it should.
Totally agree. What's the reason for dropping them? I can understand the
benefits of making Django handle its own default logic, but that doesn't
mean dropping the database default, which can be used at last stage. Also
the Django app is not always the only app accessing and writing to a
database...
--
Ticket URL: <https://code.djangoproject.com/ticket/28000#comment:15>
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/01070183c7773bb2-039dac4c-303f-4a09-89a1-92f42429c625-000000%40eu-central-1.amazonses.com.
