#30380: Support mysql query objects as strings in addition to bytes, for PyMySQL
support.
-------------------------------------+-------------------------------------
Reporter: Nathan Klug | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
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 Simon Charette):
I agree with Claude here, even if we don't have explicit support confirmed
by CI we should try to stay as compatible as possible with PyMySQL.
It already does as a pretty good job at exposing a compatible interface
through `pymysql.install_as_MySQLdb()` and in this particular we're using
an undocumented API and expecting it to behave in a certain weird way.
FWIW we [https://docs.djangoproject.com/en/2.2/ref/databases/#mysql-db-
api-drivers document we support Oracle's connector] but we don't run CI
against it and last time I checked support was completely broken and we
had to switch to `PyMySQL` for a project where `mysqlclient` could not be
used.
--
Ticket URL: <https://code.djangoproject.com/ticket/30380#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 [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/065.60945d699cba701e4d875fa0b6b6604c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
