Skip to main content
R
RR456
Inspiring
February 19, 2016
Answered

XAMPP Stacks Now Have MariaDB As Default, Any Issues?

  • February 19, 2016
  • 1 reply
  • 4060 views

Last fall Apache rolled-out a XAMPP stack (version 5.6.14) which, for the first time, had MariaDB and not MySQL as its database.  MariaDB in version 5.6.14 did not interface well the phpMyAdmin in the stack and MariaDB seemed to have instability in the user table that prevented one from adding users.  I gave up and went back to a prior XAMPP stack that had MySQL since it was far more stable and have been using that version as my test environment since.

Last fall this MariaDB instability issue was discussed in thread Favorite DB Managment Tool?

I now notice Apache Download XAMPP is exclusively using MariaDB, and not MySQL, in its current stacks including the stack that has PHP 7.0.3.  It appears if one wishes to use MySQL in a stack you must dig back in the archives.  I've not updated my stack yet because I wanted to inquire if anyone has had bug issues in the current XAMPP stacks available.

Thanks in advance for any input. 

This topic has been closed for replies.
Correct answer David_Powers

No problems whatsoever.

1 reply

David_Powers
David_PowersCorrect answer
Inspiring
February 19, 2016

No problems whatsoever.

R
RR456Author
Inspiring
February 20, 2016

Thanks again David for your input.

I installed version 7.0.3 / PHP 7.0.3 today.  Everything is very stable with the MariaDB Database server version 10.1.10.  A world of difference than last October when they first replaced MySQL with MariaDB.

Thanks again for all the assistance.

R
RR456Author
Inspiring
February 24, 2016

I spoke too soon.

There's a problem with importing dumpfiles that have been exported from MariaDB.

I had originally installed XAMPP 7.0.1, so I decided to export my databases using phpMyAdmin, uninstall XAMPP, and then install XAMPP 7.0.3. When I tried to reimport the databases, every dumpfile gave me an SQL error. I opened the dumpfiles, and checked the SQL at the point the error was reported. There was nothing wrong with it. After a lot of messing around, I tried importing some dumpfiles that had originally been created on MySQL. They imported without problem.

My final test was to go to the command prompt and import the dumpfile directly into MariaDB. It worked perfectly. I was also able to import into my remote MySQL server a file exported from MariaDB. Again, no problem. So, it would appear that there's something in the current version of phpMyAdmin that's causing grief with imports into MariaDB.

I have filed a bug report with phpMyAdmin: Import reports false SQL error with MariaDB · Issue #12025 · phpmyadmin/phpmyadmin · GitHub


On my stack upgrade it so happened that I exported using the last stack that had MySQL, not MariaDB, so on the reimport this weekend I had no problems.

I'm in a self-hosted environment and since Community Editions are not to be used in production settings, I have a conference call next Monday with MariaDB to discussion a subscription for MariaDB Enterprise 10.1.  The bug being discussed here, should I send this link to my contact at MariaDB so it can be part of the Monday conversation or is this bug pertaining to the Community Edition vis-a-vis phpMyAdmin?

Thanks in advance for any input on my question.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices