#32075 closed New feature (wontfix)
New database backend for MariaDB Connector/Python
| Reported by: | Georg Richter | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | MariaDB Connector/Python |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
MySQL and MariaDB are heading in very different directions for protocol and API. MariaDB and MySQL themselves are no longer drop-in compatible and have not been for a while, they as wider projects are heading in very different directions with different target audiences.
The existing MySQL backend supports the newer functionality of MariaDB - but these are mainly limited to SQL and not to changes and extensions in the client / server protocol. So it would be great to have a new backend for MariaDB using MariaDB Connector/Python.
Change History (2)
comment:1 by , 4 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
| Triage Stage: | Unreviewed → Someday/Maybe |
| Version: | 3.1 → master |
comment:2 by , 4 years ago
| Resolution: | needsinfo → wontfix |
|---|---|
| Triage Stage: | Someday/Maybe → Unreviewed |
We decided that MySQL and MariaDB will share the same backend. I don't see many advantages in duplicating their code. It sounds like a third-party database backend is the best way to proceed.
You can start a discussion on DevelopersMailingList if you don't agree (as Nick mentioned).
Adding a new backend is not a small undertaking. It will also likely still have much duplication with the MySQL backend too, increasing the maintenance burden.
The main issue you've raised is using a different client library. Is there anything in particular that doesn't work well with the current approach?
I suggest taking your proposal to the DevelopersMailingList first to see if there is support for this.