Moving from MySQL 5.5 to MySQL 5.6. Step 6. My first bug report


After a few entrances talking about how to move from #MySQL 5.x to versión MySQL 5.6 (what I write is also valid for MySQL 5.7 although you need to know that MySQL 5.7 doesn’t work under Windows XP), I am going to tell you two reflections:

  • The acquisition of MySQL database from ORACLE has been an important step in order to improve MySQL, specially under the Windows OS, thanks to MySQL Installer.
  • However, I am surprised because, after the success of MySQL during a lot of years, the error message are very inexpresives. That’s a common complaint in the MySQL world.

My first bug

After writting the entrance Moving from MySQL 5.5 a MySQL 5.6 step 5 talking about config file, I report my first  #Bug at!

In my opinion, the error reported is critical and it should be fixed on newer versions. Basically, this error can be corrected if during the installation process, the process ask for the datadir option (where the databases will be stored). In my case, I use to create partitios on my hard disk splitting the OS from data, and this way, the server is on on unit and the data is on another unit.

Of course, modifying the my.ini file solve this issue, also modifying the configuration to your needs (in case you should). Also, it could be great if in the log file they explain the error better, reporting something like “Data dir path … not found“!

But the thruth is that for novice users, this kind of experiences discourage to keep on working with MySQL. Also, I have tried #MariaDB and, even on the same virtual machine where I have installed MySQL, both works perfectly!! Why does MySQL allow to have several versions installed on the same server? The both can work perfectly because every one need a different port. So, where is the problem?

I haven’t tried MariaDB in deep, but I should, specially becuase several Linux distributions are changing MySQL to MariaDB.

i hope your opinions, and … have a nice day!