On that forum my username is coder1 Apache Friends Support Forum A thread at Apache Friends Support Forum, started October 23rd fully discusses this issue. Currently, MariaDB and MySQL server apparently are not playing nice in this area. Thus, I believe they're trying to make MariaDB 10.x compatible enough with MySQL server to properly operate the User Management function. No one in their right mind would provide privileges to new users at the global level.Ĭurrently Beltran Rueda, project manager at Bitnami About the XAMPP project, is working on this User Management problem since I'm quite certain they could replicate the bug at Bitnami brought to their attention by myself and another individual. Obviously the User Management function is a vital component.
Sometimes it's there and on other boot-ups table db is empty. Users data is apparently suppose to reside in table db of database MySQL. That said, the User Management bug in MariaDB 10.x is this: creating users and then drilling down and assigning them privileges specific to particular databases and/or tables might work when one first creates the user (and that's not a certainty).
As Rob noted, the trend is clearly in that direction and, performance, as well as, optimal resource usage, because of improved stored engine properties, likely makes MariaDB better from a market performance and budgetary standpoint. I'm assuming you have, or soon will have, clients inquiring as to deployment of MariaDB. Way above my skill set however, I believe MariaDB has to be compatible with MySQL server or things go horribly wrong. I don't believe this problem is a function of the db being in a stack or a particular GUI causing the problem since I've used both current versions of PMA and HeidiSQL and the same problem occurs. Some of us have discovered a critical problem with regard to User Management.
#NAVICAT FOR MYSQL 10.1.8 ZIP#
And then, being so frustrated I downloaded the zip of 10.1.8 and replaced it in the XAMPP stack. Both in a XAMPP stack version 5.6.14 where MariaDB 10.0.17 was included. Been dealing with MariaDB for about 2 weeks, versions 10.0.17 and 10.1.8. It seems as though your experience with XAMPP and MariaDB was a case of XAMPP rushing ahead with buggy versions without thoroughly testing them first.
They wait to see if critical bugs surface before committing to updating. Most hosting companies are very cautious about updating live servers to the most recent version of open source software. The Enterprise edition, on the other hand, is meant to be the stable public release. The Community Edition focuses on "fast innovation, including both mature, tested enhancements and cutting-edge experimental technologies", whereas the Enterprise edition integrates "the most stable of these advances in a curated, enterprise-grade product, bringing reliability and ease of deployment to customers." In other words, the Community edition is like a public beta it might have bugs. The MariaDB website provides a useful description of the difference between Community and Enterprise editions. XAMPP is not recommended for production use because it has very loose security settings, but the components it contains are exactly the same as used on millions of live web servers. If you don't want/need the support package, you can run the Community Edition for commercial purposes. What you're getting with the MySQL Standard Edition is an annual support package. The GPL Licence also allows distributors to charge fees. It is distributed under the GPL Licence, which grants unlimited permission to run the software. You have misunderstood the terms of the licence for the MySQL Community Edition. Thus the purchase of Standard Edition at an annual entry cost of $2,000.00 US dollars MySQL :: MySQL Editions. It appears once you are conducting commercial activity the MySQL community edition provided in XAMPP should no longer be used (also not recommended for production use anyway). Been trying to research for small business annual subscription costing of both MySQL and MariaDB.
0 kommentar(er)
