MySQL Community Server 5.1.65
# Functionality Added or Changed* Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. Download
View ArticleMySQL Community Server 5.1.63
# Bugs Fixed* Security Fix: Bug #64884 was fixed.* Security Fix: Bug #59387 was fixed.* InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation...
View ArticleMySQL Community Server 5.1.62
# Functionality Added or Changed* yaSSL was upgraded from version 1.7.2 to 2.2.0. # Bugs Fixed* Security Fix: Bug #13510739 and Bug #63775 were fixed.* Incompatible Change: An earlier change (in MySQL...
View ArticleMySQL Community Server 5.1.61
# Bugs Fixed* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY...
View ArticleMySQL Community Server 5.1.60
# Bugs Fixed* InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the...
View ArticleMySQL Community Server 5.1.59
# Bugs Fixed* InnoDB Storage Engine: The ârandom read-aheadâ feature that was removed from the InnoDB Plugin is now available again. Because it is only helpful for certain workloads, it is turned...
View ArticleMySQL Community Server 5.1.57
# Bugs fixed:- InnoDB Storage Engine: Replication: Trying to update a column, previously set to NULL, of an InnoDB table with no primary key caused replication to fail with Can't find record in...
View ArticleMySQL Community Server 5.1.56
# Bugs fixed:* InnoDB Storage Engine: InnoDB returned values for ârows examinedâ in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate...
View ArticleMySQL Community Server 5.1.55
# Bugs fixed:* Incompatible Change: When auto_increment_increment is greater than one, values generated by a bulk insert that reaches the maximum column value could wrap around rather producing an...
View ArticleMySQL Community Server 5.1.54
# Functionality added or changed:* Support for the IBMDB2I storage engine has been removed.* The pstack library was nonfunctional and has been removed, along with the --with-pstack option for...
View ArticleMySQL Community Server 5.1.53
# Bugs fixed:- Replication: SET PASSWORD caused row-based replication to fail between a MySQL 5.1 master and a MySQL 5.5 slave.* This fix makes it possible to replicate SET PASSWORD correctly, using...
View ArticleMySQL Community Server 5.1.52
# Bugs fixed:- InnoDB Storage Engine: InnoDB incorrectly reported an error when a cascading foreign key constraint deleted more than 250 rows.- InnoDB Storage Engine: A SELECT ... FOR UPDATE statement...
View ArticleMySQL Community Server 5.1.51
# Bugs fixed:* Incompatible Change: Replication: As of MySQL 5.5.6, handling of CREATE TABLE IF NOT EXISTS ... SELECT statements has been changed for the case that the destination table already...
View ArticleMySQL Community Server 5.1.50
# Bugs fixed:* Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now...
View ArticleMySQL Community Server 5.1.49
# Bugs fixed:* Replication: When using unique keys on NULL columns in row-based replication, the slave sometimes chose the wrong row when performing an update. This happened because a table having a...
View ArticleMySQL Community Server 5.1.48
# Bugs fixed:* Important Change: Replication: MyISAM transactions replicated to a transactional slave left the slave in an unstable condition. This was due to the fact that, when replicating from a...
View ArticleMySQL Community Server 5.1.47
# Bugs fixed:* Important Change: Replication: When invoked, CHANGE MASTER TO and SET GLOBAL sql_slave_skip_counter now cause information to be written to the error log about the slave's state prior to...
View ArticleMySQL Community Server 5.1.46
#InnoDB Plugin Notes:* InnoDB Plugin has been upgraded to version 1.0.7. This version is considered of General Availability (GA) quality. The InnoDB Plugin Change History may contain information in...
View ArticleMySQL Community Server 5.1.45
# Bugs fixed:* Partitioning: Attempting to drop a partitioned table from one connection while waiting for the completion of an ALTER TABLE that had been issued from a different connection, and that...
View ArticleMySQL Community Server 5.1.44
# Bugs fixed:* Partitioning: When an ALTER TABLE ... REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up...
View ArticleMySQL Community Server 5.1.43
# Bugs fixed:* Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us...
View ArticleMySQL Community Server 5.1.42
# Bugs fixed:* Performance: When the query cache is fragmented, the size of the free block lists in the memory bins grows, which causes query cache invalidation to become slow. There is now a 50ms...
View ArticleMySQL Community Server 5.1.41
# Functionality added or changed:* The InnoDB buffer pool is divided into two sublists: A new sublist containing blocks that are heavily used by queries, and an old sublist containing less-used blocks...
View ArticleMySQL Community Server 5.1.40
Bugs fixed:* Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when request help on the command with the --help...
View ArticleMySQL Community Server 5.1.39
Bugs fixed:* Partitioning: An INSERT ... SELECT statement on an empty partition of a partitioned table failed with ERROR 1030 (HY000): Got error 124 from storage engine. This issue also caused queries...
View ArticleMySQL Community Server 5.1.38
#Functionality added or changed: * The InnoDB Plugin is included in MySQL releases, in addition to the built-in version of InnoDB that has been included in previous releases. This version of the...
View ArticleMySQL Community Server 5.1.37
* Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE STATUS....
View ArticleMySQL Community Server 5.1.36
Functionality added or changed: * Important Change: Replication: Previously, incident log events were represented as comments in the output from mysqlbinlog, making them effectively silent when...
View ArticleMySQL Community Server 5.1.35
* The .msi installer does not detect an existing root password on the initial configuration attempt. To work around this, install and configure MySQL as normal, but skip any changes to security....
View ArticleMySQL Community Server 5.1.34
* Replication: Important Note: Binary logging with --binlog_format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or...
View ArticleMySQL Community Server 5.1.33
Functionality added or changed: * mysql-test-run.pl now supports an --experimental=file_name option. It enables you to specify a file that contains a list of test cases that should be displayed with...
View ArticleMySQL Community Server 5.1.32
Functionality added or changed: * Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the...
View ArticleMySQL Community Server 5.1.31
Functionality added or changed: * A new status variable, Queries, indicates the number of statements executed by the server. This includes statements executed within stored programs, unlike the...
View ArticleMySQL Community Server 5.1.30
# New! Partitioning to improve performance and management of very large database environments# New! Row-based/Hybrid Replication for improved replication security# New! Event Scheduler to create and...
View ArticleMySQL Community Server 5.0.91
# Bugs fixed:* Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be...
View ArticleMySQL Community Server 5.0.90
# Bugs fixed:* Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us...
View ArticleMySQL Community Server 5.0.89
# Bugs fixed:* Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872) See also Bug#41049.* Building MySQL on Fedora Core 12 64-bit would due to errors in comp_err....
View ArticleMySQL Community Server 5.0.88
# Bugs fixed:* Security Fix: MySQL clients linked against OpenSSL did not check server certificates presented by a server linked against yaSSL. (Bug#47320)* MySQL Cluster: When a data node had written...
View ArticleMySQL Community Server 5.0.87
Bugs fixed:# Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when request help on the command with the --help...
View ArticleMySQL Community Server 5.0.86
# Bugs fixed:* Performance: For MyISAM tables with bulk_insert_buffer_size values larger than 256KB, the performance of bulk insert operations such as multiple-row INSERT and INSERT ... SELECT...
View ArticleMySQL Community Server 5.0.85
Bugs fixed:* Important Change: Uninstalling MySQL using the MySQL installer on Windows would delete the my.ini file. The file is no longer deleted. In addition, when a new installation is conducted,...
View ArticleMySQL Community Server 5.0.84
Bugs fixed:Performance: The InnoDB adaptive hash latch is released (if held) for serveral potentially long-running operations. This improves throughput for other queries if the current query is...
View ArticleMySQL Community Server 5.0.77
This is a bugfix release for the current production release family. It replaces MySQL 5.0.67 (binary) and 5.0.75 (source-only).Functionality added or changed: * Security Enhancement: To enable...
View ArticleMySQL Community Server 5.0.67
This is a bugfix release for the current production release family. It replaces MySQL 5.0.51b.Functionality added or changed: * Security Enhancement: To enable stricter control over the location from...
View ArticleMySQL Community Server 5.0.51b
Bugs fixed: * On Windows, the installer attempted to use JScript to determine whether the target data directory already existed. On Windows Vista x64, this resulted in an error because the installer...
View ArticleMySQL Community Server 5.0.51a
Bugs fixed: * Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server...
View ArticleMySQL Community Server 5.0.45
Functionality added or changed: *MySQL Cluster: The server source tree now includes scripts to simplify building MySQL with SCI support. For more information about SCI interconnects and these build...
View ArticleMySQL Community Server 5.0.41
Functionality added or changed: - If you use SSL for a client connection, you can tell the client not to authenticate the server certificate by specifying neither --ssl-ca nor --ssl-capath. The server...
View ArticleMySQL Community Server 5.0.37
Functionality added or changed:- Added the SHOW PROFILES and SHOW PROFILE statements to display statement profile data, and the accompanying INFORMATION_SCHEMA.PROFILING table. Profiling is controlled...
View Article
