MySQL Shell 8.0 Release Notes
The schema MYSQL_AUTOPILOT
is excluded by
dump and load operations with ocimds:true
.
(Bug #37278169)
As of this release, the upgrade checker utility writes all compatibility issues and fixes to the log file, instead of only writing to the console. (Bug #37154456)
If convertBsonTypes
was enabled, the JSON
import utility failed when importing negative BSON values.
An error similar to the following was returned:
ValueError: Unexpected data, expected to find an integer string processing extended JSON for $numberInt at offset 25
(Bug #37243264)
Under certain circumstances, such as a large amount of data
chunking, the maxRate
dump option did not
properly limit the throughput due to a gap between the start of
the dump and the start of the data dump. As of this release,
maxRate
is used only when data is being
dumped.
(Bug #37216767)
MySQL Shell could hang when running a dump with
consistent: true
under an account which
lacked privileges to execute FLUSH TABLES WITH READ
LOCK
.
As of this release, query events are checked only if they
contain data, and GRANT
and
REVOKE
statements are flagged as unsafe.
(Bug #37158908)
As of this release, the Google V8 JavaScript engine is replaced by Oracle GraalVM. (Bug #34370637)
In MySQL Shell 8.0.40, RPM installation failed on Oracle Linux 8 due to a dependency on Python 3.9. As of this release, MySQL Shell bundles Python 3.13. (Bug #37479400)
It was not possible to start MySQL Shell on Oracle Linux 8
running on ARM platforms if PAGE_SIZE
was set
to 64K. An error similar to the following was displayed:
mysqlsh: error while loading shared libraries: libantlr4-runtime.so.4.10.1: ELF load command alignment not page-aligned
(Bug #36792750)