• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Your PHP MySQL library version 5.0.90 differs from your MySQL server version 5.1.50.

H

hakank

Guest
Hello guys,

I upgraded my mysql version the original version to 5.1 by following the instructions from the page http://www.atomicorp.com/wiki/index.php/Mysql. I see "Your PHP MySQL library version 5.0.90 differs from your MySQL server version 5.1.50. This may cause unpredictable behavior." warning at the bottom of phpmyadmin. I read that is something normal and can be ignored but I am also having problems with phpmyadmin modifying tables and rows. The questions is: How can I revert it back to it's original version(5.0.90) without any data loss? If anyone did this before, can he/she write down the steps because I am not so experianced with linux.

Thanks.
 
Done the same upgrade myself.
There are to my knowledge structural changes going from a mysql 5.0 to 5.1 (structure changes to tables in the mysql grant/control database). The upgrade procedures handle adding the new fields and fix the old data up to the new structure. Plus all tables (in all databases) gets stamped with the new mysql compatibility version, since there are also some data typing differences between 5.0 and 5.1. Try running a "mysqlcheck --all-databases" with an admin login to see whether what state all your tables are in. Some parts of that upgrade had to be done by repairing MyIsam tables and essentially reloading (or changing by table type) all Innodb based tables, as Innodb does not support a generic "repair".

Going back to an old database version not as easy (or possible). That is what dumping all databases before an upgrade was invented for. :) To be able to downgrade mysql and then reload all databases.
 
Back
Top