Skip to main content

MySQL to MariaDB - what to expect?

Comments

5 comments

  • mtindor
    I upgraded three servers quite some time ago and have no issues. The performance of MariaDB far outweighs any isssues that could arise. I couldn't believe the difference in system load on all machines after switching. That's my personal experience. Ancient Joomla sites running DocMan broke though -- At the time that I switched, /usr/my.cnf (yes, /usr/my.cnf) contained the following after the MariaDB update: sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES And I had to change it to allow Docman to continue to work until the customer finally ditched their ancient Joomla installs. sql_mode=NO_ENGINE_SUBSTITUTION,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO I imagine for most people this would not be an issue, nor would I really recommend anybody subvert strict_trans_tables. I also had problems with some of those Joomla sites displaying strange characters after migrating from a MySQL box to a MariaDB box. I can't say that I would necessarily consider it a MySQL-to-MariaDB issue. My fix was to change the options in PHP Selector to use nd_mysql, nd_mysqli and nd_pdo_mysql modules instead of mysql, mysqli and pdo_mysql. I'll let you decide if that was really an issue occurring because of MariaDB or not. Aside from that, I had no issues with hundreds of other accounts on other servers that I've upgrade to MariaDB. Mike
    0
  • cPanelMichael
    Hello, In addition to the previous post, you may also find this document helpful: Upgrading from MySQL to MariaDB The upgrade process itself is handled through cPanel, so you can ignore the parts about running certain scripts post-upgrade. However, the rest of the document offers some details to consider when upgrading from MySQL. Thank you.
    0
  • sparek-3
    I also had problems with some of those Joomla sites displaying strange characters after migrating from a MySQL box to a MariaDB box. I can't say that I would necessarily consider it a MySQL-to-MariaDB issue. My fix was to change the options in PHP Selector to use nd_mysql, nd_mysqli and nd_pdo_mysql modules instead of mysql, mysqli and pdo_mysql.

    Thanks for this information. I wonder if this particular issue is related to missing collations or character sets. I'd be curious to know if this is a widespread issue. I'm assuming you are using CloudLinux's PHP. Is there a comparable solution to cPanel's PHP?
    0
  • mtindor
    Thanks for this information. I wonder if this particular issue is related to missing collations or character sets. I'd be curious to know if this is a widespread issue. I'm assuming you are using CloudLinux's PHP. Is there a comparable solution to cPanel's PHP?

    Yes, I am using CloudLinux's PHP. And, I'm not aware of a comparable solution to cPanel's PHP. With that said, I'm not sure there would be any issue in the first place if you were using EA3 (or EA4 MultiPHP or Native) vs CloudLinux PHP. I went into a little more detail [just a little] on my site. Google, with "", "Joomla site shows odd characters". I was strictly going from CL/CageFS/PHP Selector on a MySQL box to CL/CageFS/PHP Selector on a MariaDB box, and at the time I was running EA3 and thus didn't have MultiPHP to test against. And I didn't test the sites against Native. mike
    0
  • DWaters
    Expect MySQL Workbench to cease functioning correctly.
    0

Please sign in to leave a comment.