---
- branch: MAIN
  date: Fri Jan 21 11:23:50 UTC 2022
  files:
  - new: '1.42'
    old: '1.41'
    path: pkgsrc/databases/mysql57-client/Makefile
    pathrev: pkgsrc/databases/mysql57-client/Makefile@1.42
    type: modified
  - new: '1.37'
    old: '1.36'
    path: pkgsrc/databases/mysql57-client/Makefile.common
    pathrev: pkgsrc/databases/mysql57-client/Makefile.common@1.37
    type: modified
  - new: '1.24'
    old: '1.23'
    path: pkgsrc/databases/mysql57-client/PLIST
    pathrev: pkgsrc/databases/mysql57-client/PLIST@1.24
    type: modified
  - new: '1.48'
    old: '1.47'
    path: pkgsrc/databases/mysql57-client/distinfo
    pathrev: pkgsrc/databases/mysql57-client/distinfo@1.48
    type: modified
  - new: '1.43'
    old: '1.42'
    path: pkgsrc/databases/mysql57-server/Makefile
    pathrev: pkgsrc/databases/mysql57-server/Makefile@1.43
    type: modified
  id: 20220121T112350Z.c9ccdaaf4216816a2e341271875370cd9e930d60
  log: "mysql57: updated to 5.7.37\n\nChanges in MySQL 5.7.37\n\nAudit Log Notes\n\nPreviously,
    each event logged by MySQL Enterprise Audit included the SQL statement literal
    text. To provide an alternative (because it is possible that statements contain
    sensitive information), the audit log filtering language now supports logging
    a statement's digest rather than its literal text. For example, instead of logging
    this statement:\n\nSELECT * FROM orders WHERE some_sensitive_column=1234567\nThe
    audit log plugin can log this digest:\n\nSELECT * FROM `orders` WHERE `some_sensitive_column`
    = ?\nThis is similar to what is already logged for prepared statements, for which
    parameter markers appear rather than actual data values.\n\nTo perform digest
    logging, use audit filter definitions that replace the statement literal text
    by its corresponding digest, as discussed in Replacement of Event Field Values.\n\nBecause
    text replacement occurs at an early auditing stage (during filtering), the choice
    of whether to log statement literal text or digest values applies regardless of
    log format written later (that is, whether the audit log plugin produces XML or
    JSON output).\n\nCompilation Notes\n\nBinary packages that include curl rather
    than linking to the system curl library have been upgraded to use curl 7.80.0.\n\nSQL
    Function and Operator Notes\n\nQueries making use of the MBRContains() function
    did not employ all available spatial indexes.\n\nThe FORMAT() function returned
    a formatted number without showing the thousands separator and grouping between
    separators when either the es_ES or es_MX locale was specified.\n\nPackaging Notes\n\nThe
    GnuPG build key used to sign MySQL downloadable packages has been updated. The
    previous GnuPG build key is set to expire on 2022-02-16. For information about
    verifying the integrity and authenticity of MySQL downloadable packages using
    GnuPG signature checking, or to obtain a copy of our public GnuPG build key, see
    Signature Checking Using GnuPG.\n\nDue to the GnuPG key update, systems configured
    to use repo.mysql.com may report a signature verification error when upgrading
    to MySQL 5.7.37 and higher or to MySQL 8.0.28 and higher using apt or yum. Use
    one of the following methods to resolve this issue:\n\nManually reinstall the
    MySQL APT or YUM repository setup package from https://dev.mysql.com/downloads/.\n\nDownload
    the MySQL GnuPG public key and add it your system GPG keyring.\n\nFor MySQL APT
    repository instructions, see Appendix A: Adding and Configuring the MySQL APT
    Repository Manually.\n\nFor MySQL YUM repository instructions, see Upgrading MySQL
    with the MySQL Yum Repository.\n\nBugs Fixed\n\nInnoDB: The buf_validate() function
    in the InnoDB sources was optimized, improving performance on debug builds.\n\nThanks
    to Hobert Lu for the contribution.\n\nPartitioning: Creating a table with nondeterministic
    functions in generated column expressions should not be possible, but this was
    not enforced in all cases; a series of one or more ALTER TABLE statements could
    be employed to arrive at a partitioned table with one or more such generated columns.
    When attempting to execute the CREATE TABLE statement obtained by running SHOW
    CREATE TABLE against this table, MySQL rejected the statement with a misleading
    error message referring to the partitioning expression rather than to the problematic
    column, despite the fact that the partitioning expression itself was legal.\n\nThis
    was caused by the result of a check for any unsafe expressions defined for a generated
    column (in the internal variable thd->safe_to_cache_query), which was later checked
    again without being cleared while parsing the partition expression, leading to
    an error even when the partition expression did not refer to the problematic generated
    column expression. Now in such cases, we reset thd->safe_to_cache_query before
    parsing the partition function.\n\nThe issue of allowing the use of certain nondeterminstic
    functions (AES_ENCRYPT(), AES_DECRYPT(), RANDOM_BYTES()) in generated columns
    is handled separately.\n\nPartitioning: A query using an index other than the
    primary key of a partitioned table sometimes resulted in excessive CPU load.\n\nReplication:
    When the PAD_CHAR_TO_FULL_LENGTH SQL mode was enabled on a replica server, trailing
    spaces could be added to a replication channel窶å\x86± name in the replication
    metadata repository tables, resulting in errors in replication operations that
    identified the channel using that data. The issue has now been fixed in MySQL
    8.0 by using VARCHAR for character columns, and in MySQL 5.7 by disabling the
    SQL mode when reading from those tables. Thanks to Brian Yue for the contribution.\n\nMySQL
    5.7 did not handle the thread_stack variable in the same manner as MySQL 5.6 or
    MySQL 8.0.\n\nIt was possible in some cases to create a generated column of type
    SERIAL, which is not allowed.\n\nSee Numeric Data Type Syntax, and CREATE TABLE
    and Generated Columns, for more information\n\nStatements which commit a transaction
    implicitly or explicitly are not allowed inside a trigger or a stored function.
    Both CREATE TRIGGER and CREATE FUNCTION should report an error (ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG)
    in this case, but did not correctly handle DROP TABLESPACE.\n\nThe MySQL session
    used for online keyring migration was not closed gracefully after the migration
    was complete, resulting in an 窶廣borted connection窶� note being printed
    to the error log.\n\nSHOW PROCESSLIST could read freed memory when accessing the
    query string belonging to a connection that was in the process of deleting a prepared
    statement.\n\nPrivileges were not checked correctly for ALTER USER ... IDENTIFIED
    WITH ... BY.\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/databases'
  unixtime: '1642764230'
  user: adam