Opened 4 years ago
Last modified 3 months ago
#12500 new New feature
Support for MySQL Connector/Python
| Reported by: | geertjanvdk | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1 |
| Severity: | Normal | Keywords: | backend mysql myconnpy |
| Cc: | wwbj2r68n2@… | Triage Stage: | Someday/Maybe |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This is a feature request/proposal for including MySQL Connector/Python, a pure Python database driver) support in Django. It will make it hopefully much easyier for people to get working with Django and MySQL on all platforms.
Attached you'll find the backend which is a patched agains Django 1.2 rev 12083. For now it works well.
We'll probably put some ideas/workaround found in the original MySQL backend, back in MySQL Connector/Python.
More information and download of MySQL Connector/Python here: https://launchpad.net/myconnpy
Attachments (1)
Change History (12)
Changed 4 years ago by geertjanvdk
comment:1 Changed 4 years ago by russellm
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Someday/Maybe
Database backends should be first be maintained as external projects. Once you have demonstrated a long-term commitment to maintaining the external project, and you can demonstrate a non-trivial demand for your backend, we may consider introducing the backend into core.
comment:2 Changed 4 years ago by dulepov
- Cc wwbj2r68n2@… added
- Keywords myconnpy added
comment:3 Changed 3 years ago by mattmcc
- Component changed from Uncategorized to Database layer (models, ORM)
- Severity set to Normal
- Type set to New feature
comment:5 Changed 2 years ago by aaugustin
- Easy pickings unset
Change Easy pickings from NULL to False.
comment:6 Changed 15 months ago by aaugustin
- Resolution set to wontfix
- Status changed from new to closed
I'm not aware of "non-trivial demand" for this backend over the last three years. If I've missed it, please reopen.
comment:7 Changed 9 months ago by Daniel.Sears@…
One reason to consider this is that MySQLdb does not currently support Python 3.
comment:8 Changed 9 months ago by aaugustin
- Resolution wontfix deleted
- Status changed from closed to new
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
comment:9 Changed 4 months ago 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
comment:10 Changed 4 months ago 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).
comment:11 Changed 3 months ago 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.
Patch of a DB backend supporting MySQL Connector/Python