#23570: Schema editor drops DEFAULT from columns for backends that do support it
-------------------------------------+-------------------------------------
Reporter: mpessas | Owner: mpessas
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: invalid
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: assigned => closed
* resolution: => invalid
Comment:
The idea is that Django shouldn't leave `DEFAULT` values in the database
(see #23043). A default is only used in the `ADD COLUMN` SQL so that a
field can be added as non-null.
--
Ticket URL: <https://code.djangoproject.com/ticket/23570#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.66d1acd84bbfb272d7e64c43bc1ae57a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
