The default settings for the isntaller would install MySQL 5.7, but your provider may have specified something different or upgraded it.
Thanks. That's what I figured. Having a hard time getting getting a straight answer out of the ISP. Now, I need to try and determine if this is the ISP's standard build or the installer/tech took it upon himself to convert it to mariaDB.
What really bugs me is that I spent hours researching whether or not it would be a good idea to convert to mariaDB and going back and forth with their tech asking questions. Then, later that day I restarted mySQL and it said mariaDB. My head almost exploded. The left hand doesn't know what the right hand is doing there.
What really bugs me is that I spent hours researching whether or not it would be a good idea to convert to mariaDB and going back and forth with their tech asking questions. Then, later that day I restarted mySQL and it said mariaDB. My head almost exploded. The left hand doesn't know what the right hand is doing there.
/var/lib/mysql you can check the following files in.
RPM_UPGRADE_HISTORY (upgrade log)
RPM_UPGRADE_MARKER-LAST (upgrade log)
mysql_upgrade_info (previous mysql version)
RPM_UPGRADE_HISTORY (upgrade log)
RPM_UPGRADE_MARKER-LAST (upgrade log)
mysql_upgrade_info (previous mysql version)
Thank you! A member of the build team got back to me and said their new installs all come with maria, although they're going to be offering mySQL again in the future. Interesting.
Since I might have to live with mariaDB, the next thing to determine is if it is safe to stick with the version they installed (10.0.37) or if I need to upgrade now. We typically build a new server every 2 years.
The 5 year boundary date for 10.0 is 31 Mar 2019, so there may be no more support in just 2 months.
My other options are 10.1 and 10.2.
Does anyone have any thoughts on upgrading to 10.1 or 10.2? I have some old applications and I need to maintain compatibility.
My only concern with 10.2 is this: MariaDB enables "strict mode" by default as of version 10.2.
I don't know enough to know if this might be a concern. My layman's thoughts are that I need to go to 10.1 where the 5 year boundary is 17 Oct 2020.
Appreciate your feedback
Since I might have to live with mariaDB, the next thing to determine is if it is safe to stick with the version they installed (10.0.37) or if I need to upgrade now. We typically build a new server every 2 years.
The 5 year boundary date for 10.0 is 31 Mar 2019, so there may be no more support in just 2 months.
My other options are 10.1 and 10.2.
Does anyone have any thoughts on upgrading to 10.1 or 10.2? I have some old applications and I need to maintain compatibility.
My only concern with 10.2 is this: MariaDB enables "strict mode" by default as of version 10.2.
I don't know enough to know if this might be a concern. My layman's thoughts are that I need to go to 10.1 where the 5 year boundary is 17 Oct 2020.
Appreciate your feedback
Your sites running in Mysql will run on mariadb.
It's just too old, joomla scripts are likely to have problems. I also saw mariadb use more cpu in some databases.
I am not raising any of my servers to mariadb because of these personal experiences. The decision is yours.
It's just too old, joomla scripts are likely to have problems. I also saw mariadb use more cpu in some databases.
I am not raising any of my servers to mariadb because of these personal experiences. The decision is yours.
Strict mode can be disabled. A good guide can be found on the WHMCS website (still relevant even so): Disabling MySQL Strict Mode | Installing WHMCS | Guides & Tutorials
At this point in time, a lot of it is up to preference, though you can't roll back to MySQL. Updating MariaDB or MySQL on cPanel does not require a new build out but if you do all of these things at once with a new server then I'd suggest going with the newest available version within cPanel to maximize your relevancy.
