4 ms·
Do you happen to know of any issues beyond what I encountered setting it up? It seems to work perfectly at the moment but I'd consider switching to a different
by robertszkutak 14y ago
Do you happen to know of any issues beyond what I encountered setting it up? It seems to work perfectly at the moment but I'd consider switching to a different DB if continuing with MySQL is going to cause me headaches later on.
- dguaraglia 14y agoTo be honest, I'd recommend making the jump to Postgres as soon as you can. There are just too many reasons why MySQL is not worth ir right now (Oracle owning it, still have to trade off between data integrity and referential integrity when selecting a storage, etc.) and Postgres gets simpler and simpler with each release. At first I found the tools confusing and some of the concepts (like schemas, sequences and the user model) a bit over the top for what I needed. Now that I've gotten used to the Postgres way of doing things, none of it bothers me in the least and working with Postgres has become as second nature as working with MySQL was.
- ubernostrum 14y agoThe general complaint I've heard is that there really is no mature, stable adapter for MySQL on Python 3. Which causes a cascade of problems with supporting it in other tools.