Hi all,
I’m new to Zammad, but I’ve been around the Open Source community since the 90’s.
I’m curious about the decision to phase out MySQL in favor of Postgres. At the moment I see I can make the choice, but that MySQL will be phased out in version 7.0.
I have no clout here, so you’re welcome to tell me to pound dirt. But I’ve also been in the different database flavors for 20+ years. Not just MySQL and PostgreSQL, but also Microsoft SQL, SQLite, MongoDB, and Oracle. I’ve even got some Lotus Notes experience thrown in there. So I feel like I’m rather well versed in the database flavors available out there.
So, why PostgreSQL only? Many projects run successfully on multiple database options. I get that everyone has their preference, but MySQL has always been favored as compared to the others, for me. Probably because I can use multiple sets of tools to manage the data. I can back the data up in a number of ways. I can write quick API/SDKs to pull data from one and push data to another. With Postgres… it’s a lot more difficult to accomplish these tasks, again, in my personal experience.
Thanks for listening!
Paul
Hello,
the release notes from back when we announced the deprecation should answer your question: New Minor Release: Zammad 5.3!
Apart from that, Zammad does not support all functions for MySQL / MariaDB databases already today .
Thanks for your response! I read through it… I may have more questions than answers now than I had then, but I respect your decision to move it to a standardized database platform.
We had various issues. I was also a big fan of MySQL since my childhood, but one point e.g. was the big gap in JSON handling between MariaDB and MySQL. Most people (AND also our customers) think that these both behave equal, but there are major differences in database table generation.
MySQL has JSON columns, MariaDB had some text columns with JSON settings. Also rails has issues with the JSON handling in MySQL/MariaDB.
There was also a big topic with the InnoDB and MySQL which made it very complex to switch to utf8mb4, but I have no details there.
Then there were some column type difference. IIRC Postgres has some nice array columns which are very performant and in MySQL/MariaDB we had to built workaround via JSON columns which made the code complex.
Developer origin scope also made an impact, since we have many Postgres developers here and not so much MySQL any more. At some point the team voted to focus on one DB and get good in that.
1 Like