Re: [Django] #12500: Support for MySQL Connector/Python
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.1
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
I'm not aware of "non-trivial demand" for this backend over the last three
years. If I've missed it, please reopen.
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.1
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Daniel.Sears@…):
One reason to consider this is that MySQLdb does not currently support
Python 3.
See https://python3wos.appspot.com/
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:7>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* status: closed => new
* resolution: wontfix =>
Comment:
Hmm. In fact, I'm going to reopen this myself, for the reasons explained
here:
https://groups.google.com/d/msg/django-developers/8r_RVmUe5ys/09lCwJl-L1kJ
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:8>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Daniel.Sears@…):
This looks like a moot point now that Oracle is shipping their own Django
back-end for MySQL:
http://dev.mysql.com/doc/connector-python/en/connector-python-django-
backend.html
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:9>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
I still believe we should switch Django's built-in MySQL backend to MySQL
Connector, because it’ll provide a better experience for MySQL users,
especially under Python 3.
An external backend is less discoverable than a built-in one, all the more
if it isn't even mentioned in the docs (we could fix that in the short
term).
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:10>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by anonymous):
The latest releases of PyMySQL work with Django + Python 3.3. So if the
backend changes, it would be nice if PyMySQL can remain compatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:11>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by timo):
#22370 details a failing test with the connector (unclear to me if the
problem is ours or theirs).
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:12>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by giuliettamasina):
Note that MySQL Connector from Oracle does not work with Django 1.7, due
to the various TEST_* settings being deprecated. See ticket #22584 for
more info on this.
(I have sent a bug report to Oracle as well.)
It might not even be a good idea to refer to this adapter in the 1.7
documentation, as is currently done here:
https://docs.djangoproject.com/en/1.7/ref/databases/#mysql-db-api-drivers
Until fixed on Oracle's side, following the documentation's advice for
Python 3 will result in non-functioning tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:13>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* cc: markus.magnuson@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:14>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by methane):
FYI, MySQL Connector/Python 1.2.2 GA has been released.
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:15>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: backend mysql | Someday/Maybe
myconnpy | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* cc: cmawebsite@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:16>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.1
(models, ORM) |
Keywords: backend mysql | Triage Stage:
myconnpy | Someday/Maybe
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by collinanderson):
I think we should close this now that we officially recommend mysqlclient.
(mysqlclient works on Python 3.)
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:17>
Django
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: nobody
Component: Database layer | Version: 1.1
(models, ORM) |
Keywords: backend mysql | Triage Stage:
myconnpy | Someday/Maybe
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => wontfix
--
Ticket URL: <https://code.djangoproject.com/ticket/12500#comment:18>