Download MySQL 5.5.10

MySQL is an open source relational database management system (RDBMS) that runs as a server providing multi-user access to a of databases. MySQL , now owned by Corporation.

MySQL is being used in some free software project like Joomla, WordPress, pBB, Drupal and other software built on the LAMP software stack. MySQL is also used in many high-profile, large-scale World Wide Web products, including Wikipedia, Google (though not for srches) and Facebook.

Homepage: mysql
Type: Relational Database Management System (RDBMS)
: GNU eral Public (version 2, with linking exception) or proprietary EULA
Written in: C, C++
Operating system: Cross-platform
Languages: English
Size: 121.60 MB
Download: (x86, 32-bit), Mirror | Mac OS X 10.6(x86, 32-bit), Mirror Support: Click Here
Bugs fix's in this version:# Bugs fixed:

* InnoDB Storage Engine: Raised the of I/O requests that ch AIO helper thrd could process, from 32 to 256. The new limit applies to Linux and Unix platforms; the limit on remains 32.
* InnoDB Storage Engine: InnoDB returned values for “rows examined” in the query plan that were higher than expected. values were trted in an inconsistent way. The inaccurate statistics could trigger “false positives” in combination with the MAX_JOIN_SIZE setting, because the queries did not rlly examine as many rows as reported.
* Repliion: When using the statement-based logging format, INSERT ON DUPLIE UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.)
* Repliion: Formerly, STOP SLAVE stopped the slave I/O thrd first and then stopped the slave SQL thrd; thus, it was possible for the I/O thrd to stop after repliing only part of a transaction which the SQL thrd was executing, in which case—if the transaction could not be rolled back safely—the SQL thrd could hang.
Now, STOP SLAVE stops the slave SQL thrd first and then stops the I/O thrd; this guarantees that the I/O thrd can fetch any remaining events in the transaction that the SQL thrd is executing, so that the SQL thrd can finish the transaction if it cannot be rolled back safely.
* DES_DECRYPT() could crash if the argument was not produced by DES_ENCRYPT().
* The server and client did not always properly negotiate authentiion plugin names.
* --autocommit=ON did not work (it set the global autocommit value to 0, not 1).
* A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with values:
SELECT DISTINCT col_name ... ORDER BY col_name DESC;
* SHOW PRIVILEGES did not display a row for the PROXY privilege.
* SHOW PROFILE could trune source file names or fail to show function names.
* DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a yr, month, or day part of zero.
* The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregate functions were not being rejected.
* Memory s detected by Varind, some of which could cause incorrect query results, were corrected.
* The DEFAULT_CHARSET and DEFAULT_COLLATION CMake options did not work.
* An OUTER JOIN query using WHERE column IS could return an incorrect result.
* Starting the server with the --defaults-file=file_name option, where the file name had no extension, caused a server crash.
* Outer joins with an empty table could produce incorrect results.
* In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash.
* When mysqladmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command.
* Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued.
* Parsing nested regular expressions could ld to recursion resulting in a stack overflow crash.
* The fix for Bug#25192 caused load_defaults() to add an argument separator to distinguish options loaded from configure files from those provided on the command line, whether or not the appliion needed it.
* The mysql client went into an infinite loop if the standard input was a directory.
* Outer joins on a unique could return incorrect results.
* The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results.
* Some RPM installation scripts used a hardd value for the data directory, which could result in a failed installation for users who have a nonstandard data directory loion. The same was true for other configuration values such as the PID file name.
* On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected.
* Sorting using ORDER BY AVG(DISTINCT decimal_col) caused a server crash or incorrect results.
* When using ExtractValue() or UpdateXML(), if the XML to be rd contained an incomplete XML comment, MySQL rd beyond the end of the XML string when processing, lding to a crash of the server.
* DATE_ADD() and DATE_SUB() return a string if the first argument is a string, but incorrectly returned a binary string. Now they return a character string with a collation of connection_collation.