Documentation Home
MySQL Shell Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 0.6Mb
PDF (A4) - 0.6Mb


MySQL Shell Release Notes  /  Changes in MySQL Shell 8.0.40 (2024-10-15, General Availability)

Changes in MySQL Shell 8.0.40 (2024-10-15, General Availability)

Utilities Added or Changed Functionality

  • As of this release, the MYSQL_OPTION schema is excluded by the dump utilities when ocimds: true and is automatically excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37023079)

Utilities Bugs Fixed

  • Under certain circumstances, using zstd compression, the dump utilities could generate corrupted data files. (Bug #36836188)

  • Attempting to run the dump or copy utilities from MySQL Shell 8.0.x against a more recent version of the server, such as 8.4.0, could result in a syntax error.

    Many breaking changes have been made to MySQL syntax and configuration between 8.0.37 and 8.4.x, and higher, such as replacing SHOW MASTER STATUS with SHOW BINARY LOG STATUS, for example. There were also many removals. See the release notes for those server versions for more information.

    As of this release, the dump and copy utilities raise an error when such incompatibilities are detected and recommend the appropriate MySQL Shell upgrade.

    Important

    It is always recommended to use the latest version of MySQL Shell.

    (Bug #36701854)

Bugs Fixed

  • MySQL Shell failed to start if installed by MSI on Microsoft Windows 11 with Visual Studio Redistributable version 14.3x or lower. On Windows platforms, MySQL Shell requires Visual Studio Redistributable version 14.4x or higher.

    See Microsoft Visual C++ Redistributable latest supported downloads. (Bug #37049411)

  • The MySQL Shell MSI progress dialogs displayed numbered placeholders instead of the installation values. (Bug #37033676)

  • When running MySQL Shell over SSH, if a command was entered on the command line, but not executed, closing the SSH session could result in the command being executed without user input. (Bug #36861912)

  • The URI parser threw an exception if the URI contained an unescaped @ character. (Bug #36105235)