2018-07-08 16:43:22 by Takahiro Kambe | Files touched by this commit (2) |
Log message:
databases/mysql57-client: fix build problem of mysql57-server
Fix build problem of mysql57-server on prior to OpenSSL 1.1 systems.
|
2018-06-14 15:13:35 by Jonathan Perkin | Files touched by this commit (2) | |
Log message:
mysql57-client: Restore patch deleted in last update.
Fixes, again, the build on SmartOS. It would be nice if people would stop
removing patches for issues I've already spent time fixing.
|
2018-04-29 23:44:12 by Adam Ciarcinski | Files touched by this commit (10) | |
Log message:
mysql57: updated to 5.7.22
Changes in MySQL 5.7.22:
Deprecation and Removal Notes
These compatibility SQL modes are now deprecated and will be removed in MySQL \
8.0: DB2, MAXDB, MSSQL, MYSQL323, MYSQL40, ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, \
NO_KEY_OPTIONS, NO_TABLE_OPTIONS. These deprecations have two implications:
Assigning a deprecated mode to the sql_mode system variable produces a warning.
With the MAXDB SQL mode enabled, using CREATE TABLE or ALTER TABLE to add a \
TIMESTAMP column to a table produces a warning.
Statements that use these deprecated SQL modes may fail when replicated from a \
MySQL 5.7 master to a MySQL 8.0 slave, or may have different effects on master \
and slave. To avoid such problems, applications that use the modes deprecated in \
MySQL 5.7 should be revised not to use them.
Test Suite Notes
Reduction of compiler and platform differences in GIS handling of floating-point \
results enables simplification of related test cases that no longer need \
rounding to avoid spurious test failures.
X Plugin Notes
X Plugin connection attempts using the X Protocol did not return an error when \
the default database specified in the connection options was invalid, and the \
connection was allowed with a null default database. Connection attempts using \
the classic MySQL protocol did return an error and disallowed the connection. X \
Protocol connection attempts now also disallow the connection if an invalid \
schema is specified.
Functionality Added or Changed
Replication: Changes introduced in version 8 which enable XCom to identify \
members using the concept of an incarnation have been merged in to version 5.7. \
These underlying changes add a UUID to members each time they join a group and \
this information can be used to distinguish among different member incarnations.
Replication: It is now possible to specify whether information written into the \
binary log enables replication slaves to parallelize based on commit timestamps, \
or on transaction write sets.
JSON: The JSON_MERGE() function is renamed to JSON_MERGE_PRESERVE().
JSON: Added the JSON utility function JSON_PRETTY(), which prints an existing \
JSON value, or any string that can successfully be parsed as a JSON document, in \
a format that can be easily read by humans. Each JSON object member or array \
value is displayed on a separate line of the output; each child object or array \
is intended 2 spaces with respect to its parent.
Bugs Fixed
|
2018-02-25 02:15:22 by Mark Davies | Files touched by this commit (7) |
Log message:
mysql57-{client,server}: support openssl 1.1
|
2018-02-02 00:01:39 by Jonathan Perkin | Files touched by this commit (1) |
Log message:
mysql57-client: Disable compiler detection on SunOS.
|
2018-01-16 17:29:42 by Adam Ciarcinski | Files touched by this commit (10) | |
Log message:
mysql57: updated to 5.7.21
MySQL 5.7.21
Audit Log Notes
* MySQL Enterprise Audit now supports compression and encryption of audit log \
files. Encryption is based on a user-defined password. To use this feature, the \
MySQL keyring must be enabled because audit logging uses it for password \
storage. MySQL Enterprise Audit also now supports logging in JSON format, in \
addition to the existing XML formats. For JSON format, functions are available \
that provide runtime log reading capabilities. For additional information, see \
MySQL Enterprise Audit.
Configuration Notes
* For RHEL, SLES, and Fedora RPMs, the default plugin directory for debug builds \
has been changed from /usr/lib64/mysql/plugin to /usr/lib64/mysql/plugin/debug.
* The installation scripts for MySQL Enterprise Audit and MySQL Enterprise \
Firewall now create their associated tables in the mysql system database as \
InnoDB rather than MyISAM tables.
* The hardcoded memory page size of 8KB for the memory-mapped transaction \
coordinator was too small for platforms such as ARM64 and PowerPC where the page \
size is much larger. The server now invokes a system call to get the page size \
of the current platform rather than using a hardcoded value. A consequence for \
the --log-tc-size option is that the minimum and default values are now 6 times \
the page size. Also, the value must be a multiple of the page size. Thanks to \
Alexey Kopytov for the patch.
Performance Schema Notes
* The Performance Schema setup_timers table is now deprecated, to be removed in \
MySQL 8.0, as is the TICK row in the performance_timers table.
Pluggable Authentication
* For the LDAP authentication plugins, handling of the group search attribute \
indicated by the authentication_ldap_sasl_group_search_attr and \
authentication_ldap_simple_group_search_attr system variables is more flexible. \
If the group search attribute is isMemberOf, LDAP authentication directly \
retrieves the user attribute isMemberOf value and assign it as group \
information. If the group search attribute is not isMemberOf, LDAP \
authentication searches for all groups where the user is a member. (The latter \
is the default behavior.) This behavior is based on how LDAP group information \
can be stored two ways: 1) A group entry can have an attribute named memberUid \
or member with a value that is a user name; 2) A user entry can have an \
attribute named isMemberOf with values that are group names.
* The LDAP authentication plugins now permit the authentication string that \
provides user DN information to begin with a + character. In the absence of this \
character, the authentication string value is treated as is without \
modification, as it has been previously. If the authentication string begins \
with +, the plugin constructs the full user DN value from the account user name \
as the cn attribute value, together with the authentication string (with the + \
removed). The authentication string is stored as given in the mysql.user system \
table, with the full user DN constructed on the fly before authentication.
* For the LDAP authentication plugins, the group search attribute was fixed and \
not configurable. Two new system variables now enable using custom group \
filters: authentication_ldap_sasl_group_search_filter and \
authentication_ldap_simple_group_search_filter.
Security Notes
* Incompatible Change: Passwords are now restricted to a maximum of 256 \
characters for the sha256_password authentication plugin, and for the PASSWORD() \
function when old_passwords=2. Also, the number of password hashing rounds is \
capped to limit CPU time used.
* The linked OpenSSL library for the MySQL Commercial Server has been updated to \
version 1.0.2n. Issues fixed in the new OpenSSL version are described at \
http://www.openssl.org/news/vulnerabilities.html.
* This change does not affect the Oracle-produced MySQL Community build of MySQL \
Server, which uses the yaSSL library instead.
* MySQL now supports key migration between underlying keyring keystores. This \
enables DBAs to switch a MySQL installation from one keyring plugin to another. \
See Migrating Keys Between Keyring Keystores.
* MySQL Enterprise Edition now includes a keyring plugin, \
keyring_encrypted_file, that is similar to the keyring_file plugin in its use of \
a local data file for key storage, but that also encrypts the file based on a \
user-defined password. See Using the keyring_encrypted_file Keyring Plugin.
|
2018-01-01 22:18:57 by Adam Ciarcinski | Files touched by this commit (629) | |
Log message:
Revbump after boost update
|
2017-10-22 22:20:57 by Adam Ciarcinski | Files touched by this commit (7) | |
Log message:
mysql57: update to 5.7.20
Changes in MySQL 5.7.20:
Audit Log Notes
Event-matching filter rules for the audit_log plugin now support an abort \
element, which can be used to prevent qualifying events from executing. For more \
information, see Audit Log Filtering. This capability can be used, for example, \
to augment the capabilities of MySQL Enterprise Firewall, which blocks SQL \
statements on a per-user basis, by writing audit filtering rules that match \
statements and block them based on characteristics of the statements themselves.
Deprecation and Removal Notes
Previously, the --transaction-isolation and --transaction-read-only server \
startup options corresponded to the tx_isolation and tx_read_only system \
variables. For better name correspondence between startup option and system \
variable names, transaction_isolation and transaction_read_only have been \
created as aliases for tx_isolation and tx_read_only. The tx_isolation and \
tx_read_only variables are now deprecated and will be removed in MySQL 8.0. \
Applications should be adjusted to use transaction_isolation and \
transaction_read_only instead.
The query cache is now deprecated and is removed in MySQL 8.0. Deprecation \
includes these items:
* The FLUSH QUERY CACHE and RESET QUERY CACHE statements.
* The SQL_CACHE and SQL_NO_CACHE SELECT modifiers.
* These system variables: have_query_cache, ndb_cache_check_time, \
query_cache_limit, query_cache_min_res_unit, query_cache_size, query_cache_type, \
query_cache_wlock_invalidate.
* These status variables: Qcache_free_blocks, Qcache_free_memory, Qcache_hits, \
Qcache_inserts, Qcache_lowmem_prunes, Qcache_not_cached, \
Qcache_queries_in_cache, Qcache_total_blocks.
The mysql client by default strips comments in statements sent to the server, \
and this behavior is controlled using --skip-comments (strip comments), and \
--comments (preserve comments).
Comment stripping is now deprecated. This feature and the options to control it \
will be removed in a future MySQL release.
These syntax constructs for table and column references are now deprecated and \
will be removed in a future version of MySQL. Instances of these constructs \
should be changed to remove the leading period.
* .col_name
* .tbl_name
* .tbl_name.col_name
Security Notes
Certificates automatically generated by mysqld and mysql_ssl_rsa_setup now use \
X509 v3 rather than v1.
The keyring_okv plugin now supports password-protecting the key file used for \
secure connections. See Using the keyring_okv KMIP Plugin.
Bugs Fixed
|
2017-09-13 19:34:41 by Adam Ciarcinski | Files touched by this commit (8) | |
Log message:
boost: update to 1.65.1
Fixes in 1.65.1
Config:
* Version macro changes for CUDA.
* Update last known MSVC version.
* MSVC 14.11 supports structured bindings.
Context:
* Return a continuation from functions executed by resume_with.
Fiber:
* Return a continuation from functions executed by resume_with.
Smart Pointers:
* Fix Visual C++ version checks.
* Fix compilation for NVCC with host compiler clang.
Stacktrace:
* Update build testing file to detail with a MinGW issue.
* Change preprocessor file extensions to work with the installation system.
* Support FreeBSD and other OSs that do not define _GNU_SOURCE but have \
_Unwind_Backtrace function.
Thread:
* Fix bug in boost::condition_variable on Windows
|
2017-09-03 10:53:18 by Thomas Klausner | Files touched by this commit (165) |
Log message:
Follow some redirects.
|