Dear MySQL users,
MySQL Server 5.6.50, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.50 is
recommended for use on production systems.
For an overview of what's new in MySQL 5.6, please see
http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html
Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6
are available both as a "full" installer and as a "web" installer.
The full installer is significantly larger and comes bundled with
the latest software releases available. This bundle makes it easy
to download and configure a full server and development suite.
The web installer doesn't come bundled with any actual products
and instead relies on download-on-demand to fetch only the
products you choose to install. This makes the initial download
much smaller but increases install time as the individual products
will need to be downloaded.
For information on installing MySQL 5.6.50 on new servers or upgrading
to MySQL 5.6.50 from previous MySQL releases, please see
http://dev.mysql.com/doc/refman/5.6/en/installing.html
MySQL Server 5.6.50, is available in source and binary form for a number of
platforms from our download pages at
http://dev.mysql.com/downloads/mysql
We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:
http://bugs.mysql.com/report.php
The following link lists the changes in the MySQL 5.6 since
the release of MySQL 5.6.49. It may also be viewed
online at
http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-50.html
Enjoy!
Changes in MySQL 5.6.50 (2020-10-19, General Availability)
Functionality Added or Changed
* LOCK TABLES privilege checking for views was improved.
(Bug #31304432)
Bugs Fixed
* InnoDB: In session started with START TRANSACTION WITH
CONSISTENT SNAPSHOT, a range query returned a truncated
result. The end range flag was not reset at the beginning
of the index read resulting in an aborted read and
missing rows. (Bug #30950714, Bug #98642)
References: This issue is a regression of: Bug #23481444.
* In bootstrapping mode, certain multiple-statement
transactions could cause unexpected server behavior. (Bug
#31650096)
* Assigning CONCAT('') or CONCAT_WS('') to a variable set
the variable to NULL, not the empty string. (Bug
#31320716, Bug #99485, Bug #31413167, Bug #99722)
* ORDER BY queries were not executed correctly when
sort_buffer_length and max_sort_length were set to values
which caused the internal limit on the maximum number of
keys allowed per sort buffer to be set to 0. (Bug
#30175483)
* The internal method Field_tiny::pack() did not always
perform bounds checking as expected. (Bug #29948029)
References: See also: Bug #31591391.
* A large number of nested arguments in full-text search
query caused an error. (Bug #29929684)
* An assertion could be raised when the SQL layer passed
incorrect information to InnoDB about the type of
operation to be performed on a temporary table. (Bug
#22503696)
On Behalf of MySQL/ORACLE RE Team
Gipson Pulla
Edited 1 time(s). Last edit at 01/03/2021 10:15PM by Balasubramanian Kandasamy.