Changes in MySQL Shell 9.5.0 (2025-10-21, Innovation Release)

Note

These release notes were created with the assistance of MySQL HeatWave GenAI.

• Utilities Added or Changed Functionality

• Utilities Bugs Fixed

• Functionality Added or Changed

• Bugs Fixed

Utilities Added or Changed Functionality

• Upgrade check names are now grouped by categories: schema, routine, accounts, and config. (Bug #38274934)

• MySQL Shell dump utilities now support the CSV dialect, conforming to RFC4180, 'csv-rfc-unix'.

  • fieldsTerminatedBy: ,

  • fieldsEnclosedBy: "

  • fieldsOptionallyEnclosed: true

  • fieldsEscapedBy: not set

  • linesTerminatedBy: <LF>

  (Bug #38245434)

• Added the convert_invalid_accounts compatibility option to the dump utilities. This option converts accounts with unsupported authentication plugins to caching_sha2_password and locks the account. (Bug #38237729)

Utilities Bugs Fixed

• MySQL Shell could close unexpectedly when running the upgrade checker utility on a MySQL Server 5.7. The error occurred on the invalidEngineForeignKey upgrade check if a table name contained non-letter characters such as hyphens. (Bug #38442101)

• When dumping with ocimds: true, schemas and tables with ENCRYPTION disabled were updated and reported as modified, creating logging noise, even though MySQL HeatWave Service disallows enabling the statement and does not generate errors if the CREATE statement explicitly disables it.

  CREATE SCHEMA or TABLE statements with disabled ENCRYPTION option are no longer modified or reported.

  Also, roles which already exist in MySQL HeatWave Service are no longer reported as warnings. (Bug #38264847)

• Using the loadDump() utility with the dropExistingObjects option enabled resulted in an error during data loading if a loading schema did not exist. Errors were returned similar to the following:

          ERROR: Error executing SQL statement for schema `schemaName`: 
          Unknown database 'schemaName'

  (Bug #38249362)

• If a table had both a unique and a non-unique key on the same referenced column, the upgrade checker utility's foreign key check could raise a false positive error. (Bug #38194922)

• Dumping from a database other than MySQL, with binary logging enabled, could fail when SHOW MASTER STATUS was executed, due to the absence of an expected fifth column, Executed_Gtid_Set. Errors similar to the following were returned:

          get_string(4): index out of bounds (ArgumentError)

  As of this release, MySQL Shell accesses this column only if it is available. (Bug #38144597)

• The copyInstance() utility failed when copying from server version 9.3.0 with MySQL Shell 9.3.1. Error similar to the following was returned:

          Requested MySQL version '9.3.1' is newer than the maximum version 
          '9.3.0' supported by this version of MySQL Shell (ArgumentError)

  (Bug #38107377)

• Loading a dump using the collation utf8mb4_uca1400_ai_ci to MySQL failed with Unknown collation: 'utf8mb4_uca1400_ai_ci'. utf8mb4_uca1400_ai_ci is not available in MySQL.

  As of this release, the dump utilities detect unsupported collations and replace them with the nearest compatible collation available in MySQL. A warning is displayed for each collation replaced. (Bug #38089433)

• Loading a dump with the schema option and checksum verification enabled failed with a logic error. Errors were returned similar to the following:

          Unable to find schema test whose existence is being checked
          (LogicError)

  (Bug #38034277)

• If loading a dump failed, due to duplicate database objects, a second attempt would succeed even though it should have failed for the same reason. This was caused by the presence of a progress file, which the second attempt saw as evidence the load was valid.

  As of this release, the progress file is not created until just before loading begins. (Bug #37326937)

Functionality Added or Changed

• Shell plugins now support standard shell print formatting, enabling consistent output for information such as errors or warnings through the shell.print() function. (Bug #38397677)

Bugs Fixed

• When resuming an interrupted load, duplicate entries could be present in the progress file, affecting byte skipping in subsequent resumes. (Bug #38408207)

• When using anonymous arguments with the -- util copyTables command, the error message did not clearly indicate the correct usage of the options. Running the command without options now displays a clear syntax message to help avoid ambiguity. (Bug #38377905)

• It is no longer possible to override the language used in \source commands unless they are run interactively. (Bug #38182270)

• It was not possible to establish a connection to MySQL 5.6 or older. The connection required session tracker support, which is not available on these servers. Errors were returned similar to the following:

          Session tracker not supported by server

  (Bug #38144635)

• Boolean command line options were not handled consistently. (Bug #38062258)

• Tab-completion did not complete filenames for the \source command. (Bug #37345664)

• The --show-warnings option returned an error that it required an argument:

          option --show-warnings requires an argument

  (Bug #34878119)