Ponder:MYSQL Serious Bug

[raychen]

A takes about 45828.33 milliseconds on MySQL, 317.66 milliseconds on SQL Server and 729 milliseconds on Access. The test results were an average of 3 consecutive. executions of the query that returned all of the data. The Access test had to use a different query so it would run. Also the MySQL box grinds the box to a holt when running the query.

The number of rows returned by MySQL is 21433, with SQL Server 21457 and
with Access 21457. The correct number of rows is 21457. So this means that
MySQL is also reporting the incorrect number of rows.

Response from arjen lentz of MYSQL AB :If the query is deterministic, then this could mean that you've found a bug.

My question is MYSQL safe ?

[aonekilla]

well it depends ... what platform are you using ... if it is windows then i am not surprised ... there have been some known issues with that version ... but it should be known that MySql is a lightweight Database server, not to be used for really critical operations... the main thing driving the popularity of the database system is its ease of use and it is free...
One must admit that MySql has a long way to go before it can be truely considered for critical ops....
Another reason why you observed these differences could be because SQL Server is optimized to operate on the windows platform, hence most of these performance bugs might be corrected already ....

[raychen]

I figured they should be corrected but can MY SQL be clustered ?,I must admit that ORACLE is king every thing else well is lags behind but is it safe to place all my client data on my SQL ?

[aonekilla]

yeh MySql can be clustered, but i think u have to pay for that ... check here (http://www.mysql.com/network/mysql_network_silver.html) for more info .... the main thing about mysql is that it should not be used on a windows platform... it is much more stable on a linux platform