Constructive criticism vs
. flaming"> eWEEK.com: MySQL has been putting out the message that MySQL is a low-cost, commodity databasesomething that, although it isnt as full-featured or robust as the larger RDBMSes, will do just fine in many instances. But there are still plenty of DBAsIm thinking of some Slashdot comments I read recentlythat said MySQL just isnt robust enough to support transactions. They complain about data integrity in MySQL, lack of transactions/stored procedures, transactions that are prone to data loss, etc. I know that some of these are being addressed in the alpha of MySQL 5.0.
Click here to read more about the alpha of MySQL 5.0 and its features.
For us as a company, there is nothing more welcome than feedback from our userspositive or negative. If someone goes through the trouble of posting his or her thoughts about MySQL on Slashdot, it means that he or she cares and has an interest in the product becoming even better. We chastise those whom we love.
If we look at the substance of those comments, they fall into a number of categories: Some comments are a matter of taste, and there is no right or wrong answer. We listen carefully to these comments to understand what the majority of our users prefer, and sometimes we make changes to syntax, parameters or default settings accordingly.
MySQL said it fixed the bugs found in Reasonings studies. Click here to read the story and find out where to download the new version.
Some comments are based on previous versions of MySQL (or previous misconceptions about MySQL) and in such cases we try to improve our communication and product presentations. Some comments have high technical validity and feed directly into our product development plans and roadmaps. Finally, some odd comments always fall under the category of flaming. These comments typically get moderated down (on Slashdot) and get corrected by other postings.
So when people claim that MySQL is not robust enough, we understand it as a challengea claim that they wish us to prove wrong. And thats what we have been doing for the past years by adding features and modules to MySQL that make it suitable for some of the most demanding applications.
Best proof of this, in our mind, is our list of customers who depend on MySQL in their everyday business (Cisco, Yahoo, Google, Sabre, Cox Communications, Associated Press, etc.).
Database Center Editor Lisa Vaas has written about enterprise applications since 1997.
Are these charges well-founded? Any comments you want to make on plans to make MySQL more robust?