#29266: Cannot perform schema migrations without downtime using MySQL in strict
mode
-------------------------------------+-------------------------------------
Reporter: Paul Tiplady | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution:
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 Tim Graham):
You can read #470 for the historical "wontfix" decision regarding database
defaults. I just reopened that ticket in light of the discussion linked to
in comment 17. Can we close this ticket in light of that?
--
Ticket URL: <https://code.djangoproject.com/ticket/29266#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.427cf647b72e9df2e1132bd3c1c8bd8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
