Why MySQL / MariaDB support was removed?

[ArsenijSerjogin]

I can understand why it may be... But would like to know a real direction of this project. Why are MySQL and MariaDB no longer supported,

• What reasons are behind this decision?
• Is there any plans to bring them back in some future?

Thanks for answer in advice!

[WebFreak001]

No one of the maintainers uses it and it adds quite a lot of code overhead with a lot of unused & untested code parts, so we dropped it to simplify maintaining and adding features. Bringing it back is currently not planned, but if there is a good reason to bring it in again, it's not impossible to bring it back.

Can you elaborate why you want to use MariaDB over PostgreSQL? While it is possible, it's currently not a major focus to support reading existing DBs with rorm, and so we assume Postgres for new projects.

[ArsenijSerjogin]

Thanks for clarification! ❤️

I also prefer PostgreSQL, however I'm currently developing a tool where I want user to be able to choose a DB they prefer. For that I looking for an ORM which will take most of heavy lifting for a different DBs schemas and migrations most of the times (without a magic). So it's nice to know this project theoretically not against cover others dbs, even if now the focus is on the most promising ones - I can still keep it in mind.

My project for sure is not valuable enough to be a reason to add an overhead.
Wish you all the luck with your ORM!