Log Message:
mysql56: updated to 5.6.46

Changes in MySQL 5.6.46

Configuration Notes

It is now possible to compile MySQL 5.6 using OpenSSL 1.1.1, enabling \ 
compilation support for MySQL 5.6 against OpenSSL even when OpenSSL 1.0.2 \ 
reaches End of Life status at the end of 2019.

In addition, MySQL 5.6 now supports TLSv1.1 and TLSv1.2 protocols for encrypted \ 
connections. This applies to MySQL Server, MySQL clients such as mysql and \ 
mysqldump, and master/slave replication. Previously, MySQL 5.6 supported only \ 
TLSv1, so TLSv1.1/TLSv1.2 support enables use of more secure TLS protocols. It \ 
also enables connecting from MySQL 5.6 clients and replication slaves to MySQL \ 
5.7 and higher servers that have TLSv1 disabled, which previously was not \ 
possible. It also means that MySQL 5.7 and higher clients that do not want to \ 
use TLSv1 can connect to MySQL 5.6 servers.

All MySQL 5.6 builds now use OpenSSL. MySQL no longer supports using yaSSL as \ 
the SSL library, and source distributions no longer include yaSSL.

The WITH_SSL CMake option no longer permits bundled (use yaSSL) as a valid \ 
value, and the default option value has changed from bundled to system (use the \ 
version of OpenSSL installed on the host system).

Bugs Fixed

Improper locking during storage engine initialization could cause a server exit.

A query with a WHERE clause whose predicate contained a numeric value in \ 
scientific notation was not handled correctly.

VS2019 produced compilation errors with debug compilation selected due to use of \ 
the /ZI flag. Now /Z7 is used instead.

Password masking was incomplete for SHOW PROCESSLIST and some INFORMATION_SCHEMA \ 
and Performance Schema tables.

The -DWITH_EXAMPLE_STORAGE_ENGINE=1 CMake option was ignored but should not have \ 
been. If -DWITH_EXAMPLE_STORAGE_ENGINE=0 is given, the EXAMPLE storage engine is \ 
built as a plugin.