#28000: Migration forces "DROP DEFAULT" SQL
-------------------------------------+-------------------------------------
Reporter: Matteo Pietro Russo | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
Comment:
Django uses database defaults to set values on existing rows in a table.
It doesn't leave the default values in the database so dropping the
default is correct behavior. There might be an optimization not to
set/drop the default in this case -- I'm not sure it's needed since the
column isn't null. A separate ticket could be opened for this.
--
Ticket URL: <https://code.djangoproject.com/ticket/28000#comment:2>
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.f3be0c0083fa31665870d7ff11ede9aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
