#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
-------------------------------------+-------------------------------------
Comment (by Matteo Pietro Russo):
Ok, now I understand. For this reason, It's not a bug.
So I can't set default value on database via Django migrations, can I?
Default values are used by Django ORM, I think it's an useful improvement
if we can apply it in db via migrations (as soon as possible). Do you
agree?
MySQL backend uses base alter_field method so I can override it as
proposal.
--
Ticket URL: <https://code.djangoproject.com/ticket/28000#comment:5>
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.d4e9d22779e19d343dd2a04dfa7a3ff9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
