#27180: Check for sql_mode fails during migration with special database
connections
-------------------------------------+-------------------------------------
Reporter: gerricom | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by gerricom):
Replying to [comment:4 claudep]:
> I'm wondering if we should continue this way with this special usage.
Wouldn't the right solution to subclass the MySQL backend and adapt the
checks?
This is for sure no problem for us if we run into another problems in
future. But in this specific case I believe there can be other cases where
this error could occur. I've attached a little patch, that works for us.
--
Ticket URL: <https://code.djangoproject.com/ticket/27180#comment:6>
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/066.4b6172a51f1feb0f4872fa136fe9d7b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
