<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>MySQL Forums - Announcements</title>
        <description>MySQL related Product and Service announcements.</description>
        <link>https://forums.mysql.com/list.php?3</link>
        <lastBuildDate>Wed, 20 May 2026 19:47:12 +0000</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://forums.mysql.com/read.php?3,741785,741785#msg-741785</guid>
            <title>Announcing April 2026 Releases featuring MySQL Server 9.7.0, 8.4.9 and 8.0.46 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,741785,741785#msg-741785</link>
            <description><![CDATA[ <pre class="bbcode">

Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 9.7.0, 8.4.9, and 8.0.46
    * MySQL Shell, Router 9.7.0, 8.4.9, and 8.0.46
    * MySQL 9.7.0 Connectors
    * MySQL NDB Cluster 9.7.0, 8.4.9, 8.0.46, and 7.6.38

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.0
and 8.4 LTS too.

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.0, 8.4 and 9.7 series
will focus on security and bug fixes only. Please refer to the following
for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

As of April 2026, with version 8.0.46, MySQL 8.0 reaches End of Life (EoL). MySQL 8.0 
users are encouraged to upgrade to the latest MySQL 8.4 LTS or MySQL Innovation release.

Changes since the previous releases can be viewed online:

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

On Behalf of the MySQL Engineering Team,
Balasubramanian Kandasamy

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Mon, 27 Apr 2026 09:22:47 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,741688,741688#msg-741688</guid>
            <title>Oracle MySQL Community Early Access (EA) Builds: MySQL 9.7.0 EA now available (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,741688,741688#msg-741688</link>
            <description><![CDATA[ The MySQL 9.7.0 Community Edition Early Access (EA) Release build is now available on MySQL Labs. <br />
======================<br />
As part of our continued focus on MySQL Community collaboration, we’re pursuing a three-pronged strategy: <br />
<br />
     1. Deliver innovation by introducing developer-focused features into MySQL Community Edition  <br />
     2. Extend and enrich the ecosystem and adoption  <br />
     3. Increase transparency and encourage broader community participation<br />
     <br />
<br />
What’s new in MySQL 9.7.0 (feature highlights) <br />
======================<br />
The release notes remain the authoritative source for complete details and final behavior. Highlights include: <br />
<br />
    * Flow-control monitoring for MySQL InnoDB Cluster (Group Replication)<br />
    * MySQL JSON Duality Views<br />
    * Hypergraph Optimizer<br />
    * Telemetry (OpenTelemetry / OTLP)<br />
    * Profile-Guided Optimization (PGO)<br />
    * Multi-threaded applier: extended applier statistics (new replication observability tables)<br />
     <br />
Early Access (EA) builds: intended for early feedback <br />
======================<br />
EA builds are pre-GA / developer preview packages meant for testing and feedback before GA. They may change prior to GA and are not intended for production use. <br />
<br />
Download EA builds: <a href="https://labs.mysql.com/"  rel="nofollow">https://labs.mysql.com/</a>  <br />
<br />
Join the discussion (and help shape what’s next) <br />
======================<br />
Our next public MySQL Community discussion is on March 23:<br />
Public MySQL Community Roadmap Discussion Webinar (Edition #2) <br />
Registration: <a href="https://oracle.zoom.us/webinar/register/WN_KSzOt8qTRNm6q7ez-5ym_Q?_x_zm_rtaid=W8ywnK#/registration"  rel="nofollow">https://oracle.zoom.us/webinar/register/WN_KSzOt8qTRNm6q7ez-5ym_Q?_x_zm_rtaid=W8ywnK#/registration</a><br />
<br />
Worklogs (WL): increased transparency <br />
======================<br />
We have also resumed publishing selected MySQL Worklogs (WL) to increase transparency and invite earlier design feedback:<br />
<a href="https://dev.mysql.com/worklog/"  rel="nofollow">https://dev.mysql.com/worklog/</a>  <br />
<br />
More info and links <br />
======================<br />
    * Blog post (full context + details): <a href="https://blogs.oracle.com/mysql/mysql-community-early-access-builds"  rel="nofollow">https://blogs.oracle.com/mysql/mysql-community-early-access-builds</a>   <br />
    * EA builds download page: <a href="https://labs.mysql.com/"  rel="nofollow">https://labs.mysql.com/</a>   <br />
    * Webinar registration: <a href="https://oracle.zoom.us/webinar/register/WN_KSzOt8qTRNm6q7ez-5ym_Q?_x_zm_rtaid=W8ywnK#/registration"  rel="nofollow">https://oracle.zoom.us/webinar/register/WN_KSzOt8qTRNm6q7ez-5ym_Q?_x_zm_rtaid=W8ywnK#/registration</a>   <br />
    * Worklogs: <a href="https://dev.mysql.com/worklog/"  rel="nofollow">https://dev.mysql.com/worklog/</a>   <br />
    * Report and view bugs: <a href="https://bugs.mysql.com/"  rel="nofollow">https://bugs.mysql.com/</a>   <br />
    * MySQL on GitHub: <a href="https://github.com/mysql/"  rel="nofollow">https://github.com/mysql/</a>   <br />
    * MySQL Community Slack channel: <a href="http://mysqlcommunity.slack.com/"  rel="nofollow">http://mysqlcommunity.slack.com/</a>]]></description>
            <dc:creator>Lenka Kašparová</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 18 Mar 2026 12:38:56 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,741575,741575#msg-741575</guid>
            <title>Announcing January 2026 Releases featuring MySQL Server 9.6.0 Innovation, 8.4.8 LTS and 8.0.45 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,741575,741575#msg-741575</link>
            <description><![CDATA[ <pre class="bbcode">

Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 9.6.0 Innovation, 8.4.8 LTS, and 8.0.45
    * MySQL Shell, Router 9.6.0, 8.4.8, and 8.0.45
    * MySQL 9.6.0 Connectors
    * MySQL NDB Cluster 9.6.0, 8.4.8, 8.0.45, and 7.6.37

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.0
and 8.4 LTS too.

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.0 and 8.4 series
will focus on security and bug fixes only. Please refer to the following
for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

Changes since the previous releases can be viewed online:

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

On Behalf of the MySQL Engineering Team,
Balasubramanian Kandasamy

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Fri, 23 Jan 2026 17:56:47 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,741319,741319#msg-741319</guid>
            <title>Announcing October 2025 Releases featuring MySQL Server 9.5.0 Innovation, 8.4.7 LTS and 8.0.44 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,741319,741319#msg-741319</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 9.5.0 Innovation, 8.4.7 LTS, and 8.0.44
    * MySQL Shell, Router 9.5.0, 8.4.7, and 8.0.44
    * MySQL 9.5.0 Connectors
    * MySQL NDB Cluster 9.5.0, 8.4.7, 8.0.44, and 7.6.36

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.0
and 8.4 LTS too.

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.0 and 8.4 series
will focus on security and bug fixes only. Please refer to the following
for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

Changes since the previous releases can be viewed online:

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

On Behalf of the MySQL Engineering Team,
Balasubramanian Kandasamy

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Sat, 25 Oct 2025 11:45:29 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,741007,741007#msg-741007</guid>
            <title>Announcing July 2025 Releases featuring MySQL Server 9.4.0 Innovation, 8.4.6 LTS and 8.0.43 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,741007,741007#msg-741007</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL users,

We are pleased to announce the release of the following products: 

    * MySQL Server 9.4.0 Innovation, 8.4.6 LTS, and 8.0.43
    * MySQL Shell, Router 9.4.0, 8.4.6, and 8.0.43
    * MySQL 9.4.0 Connectors
    * MySQL NDB Cluster 9.4.0, 8.4.6, 8.0.43, and 7.6.35 

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.0
and 8.4 LTS too.

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.0 and 8.4 series
will focus on security and bug fixes only. Please refer to the following
for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

Changes since the previous releases can be viewed online:

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>
</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 22 Jul 2025 18:42:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,740585,740585#msg-740585</guid>
            <title>Announcing April 2025 Releases featuring MySQL Server 9.3.0 Innovation, 8.4.5 LTS and 8.0.42 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,740585,740585#msg-740585</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 9.3.0 Innovation, 8.4.5 LTS, and 8.0.42
    * MySQL Connectors 9.3.0
    * MySQL NDB Cluster 9.3.0, 8.4.5, 8.0.42, and 7.6.34

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.0
and 8.4 LTS too.

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.0 and 8.4 series
will focus on security and bug fixes only. Please refer to the following
for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

Changes since the previous releases can be viewed online:

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 16 Apr 2025 18:35:44 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,740132,740132#msg-740132</guid>
            <title>Announcing January 2025 Releases featuring MySQL Server 9.2.0 Innovation, 8.4.4 LTS and 8.0.41 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,740132,740132#msg-740132</link>
            <description><![CDATA[ <pre class="bbcode">
MySQL Server 9.2.0 Innovation, 8.4.4 LTS and 8.0.41, new versions of the
popular Open Source Database Management System have been released.

We are pleased to announce the release of MySQL 9.2.0 Connectors.
Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors.  These version 9.2 clients, tools, and
connectors support both MySQL Server 8.0 and 8.4 LTS.

We are also pleased to announce the release of MySQL NDB Cluster 9.2.0
Innovation, the latest GA, along with 8.4.4 LTS, 8.0.41, 7.6.33.
MySQL NDB Cluster is the distributed, shared-nothing variant of MySQL.

MySQL Server 9.2.0 and MySQL NDB Cluster 9.2.0 are Innovation releases,
which means it will have new features, deprecations/removals, and bug
fixes.

Innovation releases are supported until the next innovation release, and
are recommended for production use.

With this Innovation series, the existing 8.0 and 8.4 series will focus
on security and bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
link for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>
</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 22 Jan 2025 14:08:23 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,730672,730672#msg-730672</guid>
            <title>MySQL Shell for VS Code 1.17.1 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,730672,730672#msg-730672</link>
            <description><![CDATA[ <pre class="bbcode">

Dear MySQL users,

We are excited to announce that MySQL Shell for VS Code 1.17.1, a VS
Code extension, is now generally available in the VS Code Marketplace!

The MySQL Shell for VS Code extension builds upon the MySQL Shell 9.1.0
feature set, a component of the MySQL Server.

MySQL Shell for VS Code provides a modern notebook interface allowing
developers to interactively work with and execute SQL, JavaScript and
TypeScript against MySQL databases and the HeatWave MySQL service.

The MySQL notebooks interface provides an embedded DB Editor offering
the modern interface for interactive coding and database development.
Easily switch from SQL to JavaScript or TypeScript to query, manipulate,
and visualize your data.

Advanced OCI HeatWave Integration includes:

  - Full support for HeatWave Chat and Lakehouse Navigator
  - Easily Upload documents to HeatWave Lakehouse
  - Query HeatWave Lakehouse documents using natural language
  - Simple secure access to all your Heatwave MySQL instances via
    Bastion connections.

Download the extension directly from within VS Code by selecting the
Extensions icon in the Activity Bar and searching for MySQL Shell or
download from

<a href="https://marketplace.visualstudio.com/items?itemName=Oracle.mysql-shell-for-vs-code"  rel="nofollow">https://marketplace.visualstudio.com/items?itemName=Oracle.mysql-shell-for-vs-code</a>

For documentation on MySQL Shell for VS Code, see

<a href="https://dev.mysql.com/doc/mysql-shell-gui/en/"  rel="nofollow">https://dev.mysql.com/doc/mysql-shell-gui/en/</a>

For full documentation on MySQL Shell, see

<a href="https://dev.mysql.com/doc/mysql-shell/9.1/en/"  rel="nofollow">https://dev.mysql.com/doc/mysql-shell/9.1/en/</a>

For full documentation on MySQL Server, see

<a href="https://dev.mysql.com/doc/refman/9.1/en/"  rel="nofollow">https://dev.mysql.com/doc/refman/9.1/en/</a>

We welcome and appreciate your feedback and bug reports, see

<a href="https://bugs.mysql.com/report.php?category=Shell%20VSCode%20Extension"  rel="nofollow">https://bugs.mysql.com/report.php?category=Shell%20VSCode%20Extension</a>

MySQL Shell for VS Code is brought to you by the MySQL team at Oracle.

Enjoy!

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 06 Nov 2024 04:26:38 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,727551,727551#msg-727551</guid>
            <title>Announcing October 2024 Releases featuring MySQL Server 9.1.0 Innovation, 8.4.3 LTS and 8.0.40 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,727551,727551#msg-727551</link>
            <description><![CDATA[ <pre class="bbcode">
MySQL Server 9.1.0 Innovation, 8.4.3 LTS and 8.0.40, new versions of the
popular Open Source Database Management System have been released.

We are pleased to announce the release of MySQL 9.1.0 Connectors.
Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors.  These version 9.1 clients, tools, and
connectors support both MySQL Server 8.0 and 8.4 LTS.

We are also pleased to announce the release of MySQL NDB Cluster 9.1.0
Innovation, the latest GA, along with 8.4.3 LTS, 8.0.40, 7.6.32, 7.5.36.
MySQL NDB Cluster is the distributed, shared-nothing variant of MySQL.

MySQL Server 9.1.0 and MySQL NDB Cluster 9.1.0 are Innovation releases,
which means it will have new features, deprecations/removals, and bug
fixes.

Innovation releases are supported until the next innovation release, and
are recommended for production use.

With this Innovation series, the existing 8.0 and 8.4 series will focus
on security and bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
link for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 16 Oct 2024 17:48:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,725231,725231#msg-725231</guid>
            <title>Announcing July 2024 off-cycle Releases featuring MySQL Server 9.0.1 Innovation, 8.4.2 LTS and 8.0.39 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,725231,725231#msg-725231</link>
            <description><![CDATA[ <pre class="bbcode">

MySQL Server 9.0.1 Innovation, 8.4.2 LTS and 8.0.39,new versions of the
popular Open Source Database Management System have been released.

We are also pleased to announce the release of MySQL NDB Cluster 9.0.1
Innovation, the latest GA, along with 8.4.2 LTS, 8.0.39.
MySQL NDB Cluster is the distributed, shared-nothing variant of MySQL.

MySQL Server 9.0.1 and MySQL NDB Cluster 9.0.1 are Innovation releases,
which means it will have new features, deprecations/removals, and bug
fixes.

Innovation releases are supported until the next innovation release, and
are recommended for production use.

With this Innovation series, the existing 8.0 and 8.4 series will focus
on security and bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
link for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 24 Jul 2024 17:15:53 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,725007,725007#msg-725007</guid>
            <title>Announcing July 2024 Releases featuring MySQL Server 9.0.0 Innovation, 8.4.1 LTS and 8.0.38 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,725007,725007#msg-725007</link>
            <description><![CDATA[ <pre class="bbcode">
MySQL Server 9.0.0 Innovation, 8.4.1 LTS and 8.0.38,new versions of the
popular Open Source Database Management System have been released.

We are pleased to announce the release of MySQL 9.0.0 Connectors.
Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors.  These version 9.0 clients, tools, and
connectors support both MySQL Server 8.0 and 8.4 LTS.

We are also pleased to announce the release of MySQL NDB Cluster 9.0.0
Innovation, the latest GA, along with 8.4.1 LTS, 8.0.38, 7.6.31, 7.5.35.
MySQL NDB Cluster is the distributed, shared-nothing variant of MySQL.

MySQL Server 9.0.0 and MySQL NDB Cluster 9.0.0 are Innovation releases,
which means it will have new features, deprecations/removals, and bug
fixes.

Innovation releases are supported until the next innovation release, and
are recommended for production use.

With this Innovation series, the existing 8.0 and 8.4 series will focus
on security and bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
link for more information:

<a href="https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html"  rel="nofollow">https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 02 Jul 2024 12:42:33 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,723962,723962#msg-723962</guid>
            <title>Announcing April 2024 Releases featuring MySQL 8.4.0 and 8.0.37 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,723962,723962#msg-723962</link>
            <description><![CDATA[ <pre class="bbcode">

MySQL Server 8.4.0 and 8.0.37, new versions of the popular Open Source
Database Management System, have been released in conjunction with the
MySQL Shell, MySQL Router and MySQL 8.4.0 Connectors.

We are also pleased to announce the release of MySQL NDB Cluster 8.4.0,
the latest GA, along with 8.0.37, 7.6.30, 7.5.34. MySQL NDB Cluster is
the distributed, shared-nothing variant of MySQL.

MySQL Server 8.4.0 and MySQL NDB Cluster 8.4.0 marks the start of a new
series of LTS (Long Term Support) releases. The 8.4.X LTS releases will
focus on security and bug fixes.

The next Innovation series will have new features.

Please refer to the below MySQL Innovation and Long Term support (LTS)
blog for more information:

<a href="https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions"  rel="nofollow">https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Developers can download MySQL Enterprise Edition from

<a href="https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html"  rel="nofollow">https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>
</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 30 Apr 2024 20:33:36 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,723605,723605#msg-723605</guid>
            <title>Announcing a new webcast video that completes a deep dive into how to download and use Enterprise Manager for MySQL (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,723605,723605#msg-723605</link>
            <description><![CDATA[ Announcing a new webcast video that completes a deep dive into how to download and use Enterprise Manager for MySQL.<br />
 <br />
Learn how to monitor your MySQL fleet with 600+ MySQL metrics out of the box, monitor slow running queries using Query Analyzer and validate compliance against configuration and security best practices: <a href="https://www.youtube.com/watch?v=U5VvgjFvLNs&amp;list=PLiuPvpy8QsiVTwf_JXvRGFKFdmzM9GfCX&amp;index=4"  rel="nofollow">https://www.youtube.com/watch?v=U5VvgjFvLNs&amp;list=PLiuPvpy8QsiVTwf_JXvRGFKFdmzM9GfCX&amp;index=4</a>.<br />
<br />
Note: Enterprise Manager for MySQL is included with MySQL Enterprise Edition and MySQL Cluster Carrier Grade Edition at no additional cost.<br />
<br />
For more details on using Enterprise Manager for MySQL, please see:<br />
— Documentation: <a href="https://dev.mysql.com/doc/mysql-em-plugin/en/"  rel="nofollow">https://dev.mysql.com/doc/mysql-em-plugin/en/</a><br />
— Blog: <a href="https://blogs.oracle.com/observability/post/comprehensive-monitoring-and-compliance-management-for-mysql-databases-using-enterprise-manager"  rel="nofollow">https://blogs.oracle.com/observability/post/comprehensive-monitoring-and-compliance-management-for-mysql-databases-using-enterprise-manager</a><br />
<br />
For more details on installing Enterprise Manager, please see:<br />
— Basic Installation Guide: <a href="https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/embsc/index.html#Oracle%C2%AE-Enterprise-Manager"  rel="nofollow">https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/embsc/index.html#Oracle%C2%AE-Enterprise-Manager</a><br />
— Administration Guide: <a href="https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/emadm/index.html#Oracle%C2%AE-Enterprise-Manager"  rel="nofollow">https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/emadm/index.html#Oracle%C2%AE-Enterprise-Manager</a><br />
<br />
Thank you!]]></description>
            <dc:creator>Edwin Desouza</dc:creator>
            <category>Announcements</category>
            <pubDate>Thu, 04 Apr 2024 21:01:41 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,714993,714993#msg-714993</guid>
            <title>Announcing January 2024 Releases featuring MySQL 8.3.0 and 8.0.36 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,714993,714993#msg-714993</link>
            <description><![CDATA[ <pre class="bbcode">

MySQL Server 8.3.0 and 8.0.36, new versions of the popular Open
Source Database Management System, have been released in conjunction
with the MySQL Shell, MySQL Router and MySQL 8.3.0 Connectors.

We are also pleased to announce the release of MySQL NDB Cluster 8.3.0,
the latest GA, along with 8.0.36, 7.6.29, 7.5.33. MySQL NDB Cluster is
the distributed, shared-nothing variant of MySQL.

MySQL Server 8.3.0 and MySQL NDB Cluster 8.3.0 are Innovation releases,
which means they will have new features in addition to bug fixes. They
are supported until the next Innovation release comes out. With this new
Innovation series, the existing 8.0 series will focus on security and
bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
blog for more information:

<a href="https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions"  rel="nofollow">https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet. 

MySQL Enterprise binaries are also available on the Oracle Software Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>

</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 16 Jan 2024 17:57:30 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,710298,710298#msg-710298</guid>
            <title>Announcing October 2023 Releases featuring MySQL 8.2.0 and 8.0.35 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,710298,710298#msg-710298</link>
            <description><![CDATA[ <pre class="bbcode">
MySQL Server 8.2.0, 8.0.35 and 5.7.44, new versions of the popular Open
Source Database Management System, have been released in conjunction
with the MySQL Shell, MySQL Router and MySQL 8.2.0 Connectors.

We are also pleased to announce the release of MySQL Cluster 8.2.0, the
latest GA, along with 8.0.35, 7.6.28, 7.5.32. MySQL Cluster is the
distributed, shared-nothing variant of MySQL.

MySQL Server 8.2.0 and MySQL Cluster 8.2.0 are Innovation releases,
which means they will have new features in addition to bug fixes. They
are supported until the next Innovation release comes out. With this new
Innovation series, the existing 8.0 series will focus on security and
bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
blog for more information:

<a href="https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions"  rel="nofollow">https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet. 

MySQL Enterprise binaries are also available on the Oracle Software Delivery Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>
</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 25 Oct 2023 19:30:34 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,709550,709550#msg-709550</guid>
            <title>Announcing July 2023 Releases featuring MySQL 8.1.0 and 8.0.34 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,709550,709550#msg-709550</link>
            <description><![CDATA[ <pre class="bbcode">
MySQL Server 8.1.0, 8.0.34 and 5.7.43, new versions of the popular Open
Source Database Management System, have been released in conjunction
with the MySQL Shell, MySQL Router and MySQL 8.1.0 Connectors.

We are also pleased to announce the release of MySQL Cluster 8.1.0, the
latest GA, along with 8.0.34, 7.6.27, 7.5.31. MySQL Cluster is the
distributed, shared-nothing variant of MySQL.

MySQL Server 8.1.0 and MySQL Cluster 8.1.0 are Innovation releases,
which means they will have new features in addition to bug fixes. They
are supported until the next Innovation release comes out. With this new
Innovation series, the existing 8.0 series will focus on security and
bug fixes only.

Please refer to the below MySQL Innovation and Long Term support (LTS)
blog for more information:

<a href="https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions"  rel="nofollow">https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions</a>

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a>

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and MySQL products are available in the unified
Installer for Windows:

<a href="https://dev.mysql.com/downloads/installer/"  rel="nofollow">https://dev.mysql.com/downloads/installer/</a>

Enterprise binaries for these new releases are available on My Oracle
Support:

<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a>

Choose the “Patches &amp; Updates” tab, and then choose the “Product or
Family (Advanced Search)” side tab in the “Patch Search” portlet. 

MySQL Enterprise binaries are also available on the Oracle Software Delivery
Cloud:

<a href="https://edelivery.oracle.com/"  rel="nofollow">https://edelivery.oracle.com/</a>

Changes in the release since the previous one can be viewed online as
shown below.

<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>
</pre>]]></description>
            <dc:creator>Balasubramanian Kandasamy</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 18 Jul 2023 17:50:12 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,708789,708789#msg-708789</guid>
            <title>Announcing April 2023 Releases featuring MySQL 8.0.33 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,708789,708789#msg-708789</link>
            <description><![CDATA[ MySQL Server 8.0.33 and 5.7.42, new versions of the popular Open Source<br />
Database Management System, have been released in conjunction with the<br />
8.0.33 Connector and Component products.<br />
<br />
We are also pleased to announce the release of MySQL Cluster 8.0.33, the<br />
latest GA, along with 7.6.26, 7.5.30. MySQL Cluster is the distributed,<br />
shared-nothing variant of MySQL.<br />
<br />
These releases are recommended for use on production systems and are<br />
available in source and binary form for a number of platforms from our<br />
MySQL Community download pages at:<br />
<br />
<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a><br />
<br />
Windows packages are available via the Installer for Windows or .ZIP<br />
(no-install) packages for more advanced needs. The point and click<br />
configuration wizards and all MySQL products are available in the<br />
unified Installer for Windows:<br />
<br />
<a href="http://dev.mysql.com/downloads/installer/"  rel="nofollow">http://dev.mysql.com/downloads/installer/</a><br />
<br />
Enterprise binaries for these new releases are available on My Oracle<br />
Support:<br />
<br />
<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a><br />
<br />
Choose the “Patches &amp; Updates” tab, and then choose the “Product or<br />
Family (Advanced Search)” side tab in the “Patch Search” portlet.<br />
<br />
MySQL 8.0.33 enterprise releases are also available on the Oracle<br />
Software Delivery Cloud:<br />
<br />
<a href="http://edelivery.oracle.com/"  rel="nofollow">http://edelivery.oracle.com/</a><br />
<br />
Changes in the release since the previous one can be viewed online as<br />
shown below.<br />
<br />
<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>]]></description>
            <dc:creator>Karen Langford</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 19 Apr 2023 10:42:45 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,707243,707243#msg-707243</guid>
            <title>Announcing January 2023 Releases featuring MySQL 8.0.32 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,707243,707243#msg-707243</link>
            <description><![CDATA[ MySQL Server 8.0.32 and 5.7.41, new versions of the popular Open Source<br />
Database Management System, have been released in conjunction with the<br />
8.0.32 Connector and Component products.<br />
<br />
We are also pleased to announce the release of MySQL Cluster 8.0.32, the<br />
latest GA, along with 7.6.25, 7.5.29, 7.4.39. MySQL Cluster is the<br />
distributed, shared-nothing variant of MySQL.<br />
<br />
These releases are recommended for use on production systems and are<br />
available in source and binary form for a number of platforms from our<br />
MySQL Community download pages at:<br />
<br />
<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a><br />
<br />
Windows packages are available via the Installer for Windows or .ZIP<br />
(no-install) packages for more advanced needs. The point and click<br />
configuration wizards and all MySQL products are available in the<br />
unified Installer for Windows:<br />
<br />
<a href="http://dev.mysql.com/downloads/installer/"  rel="nofollow">http://dev.mysql.com/downloads/installer/</a><br />
<br />
Enterprise binaries for these new releases are available on My Oracle<br />
Support:<br />
<br />
<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a><br />
<br />
Choose the “Patches &amp; Updates” tab, and then choose the “Product or<br />
Family (Advanced Search)” side tab in the “Patch Search” portlet.<br />
<br />
MySQL 8.0.32 enterprise releases are also available on the Oracle<br />
Software Delivery Cloud:<br />
<br />
<a href="http://edelivery.oracle.com/"  rel="nofollow">http://edelivery.oracle.com/</a><br />
<br />
Changes in the release since the previous one can be viewed online as<br />
shown below.<br />
<br />
<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>]]></description>
            <dc:creator>Karen Langford</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 18 Jan 2023 04:40:49 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,706469,706469#msg-706469</guid>
            <title>Announcing October 2022 Releases featuring MySQL 8.0.31 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,706469,706469#msg-706469</link>
            <description><![CDATA[ MySQL Server 8.0.31 and 5.7.40, new versions of the popular Open Source<br />
Database Management System, have been released in conjunction with the<br />
8.0.31 Connector and Component products.<br />
<br />
We are also pleased to announce the release of MySQL Cluster 8.0.31, the<br />
latest GA, along with 7.6.24, 7.5.28, 7.4.38. MySQL Cluster is the<br />
distributed, shared-nothing variant of MySQL.<br />
<br />
These releases are recommended for use on production systems and are<br />
available in source and binary form for a number of platforms from our<br />
MySQL Community download pages at:<br />
<br />
<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a><br />
<br />
Windows packages are available via the Installer for Windows or .ZIP<br />
(no-install) packages for more advanced needs. The point and click<br />
configuration wizards and all MySQL products are available in the<br />
unified Installer for Windows:<br />
<br />
<a href="http://dev.mysql.com/downloads/installer/"  rel="nofollow">http://dev.mysql.com/downloads/installer/</a><br />
<br />
Enterprise binaries for these new releases are available on My Oracle<br />
Support:<br />
<br />
<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a><br />
<br />
Choose the “Patches &amp; Updates” tab, and then choose the “Product or<br />
Family (Advanced Search)” side tab in the “Patch Search” portlet.<br />
<br />
MySQL 8.0.31 enterprise releases are also available on the Oracle<br />
Software Delivery Cloud:<br />
<br />
<a href="http://edelivery.oracle.com/"  rel="nofollow">http://edelivery.oracle.com/</a><br />
<br />
Changes in the release since the previous one can be viewed online as<br />
shown below.<br />
<br />
<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>]]></description>
            <dc:creator>Karen Langford</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 12 Oct 2022 01:44:33 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,705516,705516#msg-705516</guid>
            <title>Announcing July 2022 Releases featuring MySQL 8.0.30 (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,705516,705516#msg-705516</link>
            <description><![CDATA[ MySQL Server 8.0.30 and 5.7.39, new versions of the popular Open Source Database<br />
Management System, have been released in conjunction with the 8.0.30 Connector<br />
and Component products.<br />
<br />
We are also pleased to announce the release of MySQL Cluster 8.0.30, the latest<br />
GA, along with 7.6.23, 7.5.27, 7.4.37. MySQL Cluster is the distributed,<br />
shared-nothing variant of MySQL.<br />
<br />
These releases are recommended for use on production systems and are available<br />
in source and binary form for a number of platforms from our MySQL Community<br />
download pages at:<br />
<br />
<a href="https://dev.mysql.com/downloads/"  rel="nofollow">https://dev.mysql.com/downloads/</a><br />
<br />
Windows packages are available via the Installer for Windows or .ZIP<br />
(no-install) packages for more advanced needs. The point and click configuration<br />
wizards and all MySQL products are available in the unified Installer for<br />
Windows:<br />
<br />
<a href="http://dev.mysql.com/downloads/installer/"  rel="nofollow">http://dev.mysql.com/downloads/installer/</a><br />
<br />
Enterprise binaries for these new releases are available on My Oracle Support:<br />
<br />
<a href="https://support.oracle.com"  rel="nofollow">https://support.oracle.com</a><br />
<br />
Choose the “Patches &amp; Updates” tab, and then choose the “Product or Family<br />
(Advanced Search)” side tab in the “Patch Search” portlet.<br />
<br />
MySQL 8.0.30 enterprise releases are also available on the Oracle Software<br />
Delivery Cloud:<br />
<br />
<a href="http://edelivery.oracle.com/"  rel="nofollow">http://edelivery.oracle.com/</a><br />
<br />
Changes in the release since the previous one can be viewed online as shown<br />
below.<br />
<br />
<a href="https://dev.mysql.com/doc/#current-release-notes"  rel="nofollow">https://dev.mysql.com/doc/#current-release-notes</a>]]></description>
            <dc:creator>Karen Langford</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 27 Jul 2022 04:10:44 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,704156,704156#msg-704156</guid>
            <title>MySQL 8.0.29:  Release Notes (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,704156,704156#msg-704156</link>
            <description><![CDATA[ MySQL 8.0.29:  Release Notes<br />
- <a href="https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html</a><br />
- <a href="https://dev.mysql.com/doc/relnotes/mysql-shell/8.0/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/mysql-shell/8.0/en/news-8-0-29.html</a><br />
- <a href="https://dev.mysql.com/doc/relnotes/mysql-router/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/mysql-router/en/news-8-0-29.html</a><br />
- <a href="https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-29.html</a><br />
- <a href="https://dev.mysql.com/doc/relnotes/connector-odbc/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/connector-odbc/en/news-8-0-29.html</a><br />
- <a href="https://dev.mysql.com/doc/relnotes/connector-cpp/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/connector-cpp/en/news-8-0-29.html</a><br />
- <a href="https://dev.mysql.com/doc/relnotes/connector-python/en/news-8-0-29.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/connector-python/en/news-8-0-29.html</a>]]></description>
            <dc:creator>Edwin Desouza</dc:creator>
            <category>Announcements</category>
            <pubDate>Wed, 27 Apr 2022 03:09:36 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696019,696019#msg-696019</guid>
            <title>MySQL Workbench 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696019,696019#msg-696019</link>
            <description><![CDATA[ Dear MySQL users,<br />
<br />
The MySQL developer tools team announces 8.0.24 as our General<br />
Availability (GA) for MySQL Workbench 8.0.<br />
<br />
For discussion, join the MySQL Workbench Forums:<br />
<br />
  <a href="http://forums.mysql.com/index.php?152"  rel="nofollow">http://forums.mysql.com/index.php?152</a><br />
<br />
The release is now available in source and binary form for a number of<br />
platforms from our download pages at:<br />
<br />
  <a href="http://dev.mysql.com/downloads/tools/workbench/"  rel="nofollow">http://dev.mysql.com/downloads/tools/workbench/</a><br />
<br />
Enjoy!<br />
<br />
<br />
<pre class="bbcode">
Changes in MySQL Workbench 8.0.24 (2021-04-20, General Availability)

Functionality Added or Changed

     * The following third-party libraries were upgraded in this
       release (Bug #32317082):

          + AT-SPI
          + Cairo
          + FreeTDS
          + GDAL/OGR
          + HtmlRenderer (System.Drawing.Html)
          + iODBC
          + libgcrypt
          + Libintl
          + libgpg-error
          + Libpng
          + libssh v0.7.5-openssl1.1_patch
          + Libzip
          + PCRE (Perl Compatible Regular Expressions) Library
          + Pixman
          + PROJ.4
          + PyODBC
          + PySQLite (removed)
          + TreeViewAdv for .NET
          + VSQLite++

     * The linked OpenSSL library for MySQL Workbench has been
       updated to version 1.1.1J. Issues fixed in the new
       OpenSSL version are described at
       <a href="https://www.openssl.org/news/cl111.txt"  rel="nofollow">https://www.openssl.org/news/cl111.txt</a> and
       <a href="https://www.openssl.org/news/vulnerabilities.html"  rel="nofollow">https://www.openssl.org/news/vulnerabilities.html</a>.
       (Bug #31957287, Bug #32260611)

Bugs Fixed

     * MySQL Workbench 8.0.23 closed unexpectedly after starting
       on macOS systems. This fix adds the Python 3.7 framework
       as a prerequisite for the installation.
       (Bug #32395192, Bug #102286)

     * Unexpected output was written to the console when MySQL
       Workbench was started from the command line on Linux.
       Adjusting the log level did not stop the output. This
       issue was unrelated to log suppression and was eliminated
       by resolving a different issue. (Bug #32106379)</pre>
<br />
Enjoy and thanks for the support!<br />
<br />
On Behalf of the MySQL Engineering Team,<br />
Kent Boortz]]></description>
            <dc:creator>Kent Boortz</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 16:12:44 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696018,696018#msg-696018</guid>
            <title>MySQL Cluster 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696018,696018#msg-696018</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

 - In-Memory storage - Real-time performance (with optional
   checkpointing to disk)
 - Transparent Auto-Sharding - Read &amp; write scalability
 - Active-Active/Multi-Master geographic replication

 - 99.999% High Availability with no single point of failure
   and on-line maintenance
 - NoSQL and SQL APIs (including C++, Java, http and
   JavaScript/Node.js)

MySQL Cluster 8.0.24 has been released and can be downloaded from

 <a href="http://www.mysql.com/downloads/cluster/"  rel="nofollow">http://www.mysql.com/downloads/cluster/</a>

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

 <a href="http://dev.mysql.com/doc/relnotes/mysql-cluster/8.0/en/index.html"  rel="nofollow">http://dev.mysql.com/doc/relnotes/mysql-cluster/8.0/en/index.html</a>

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

 <a href="http://www.mysql.com/products/cluster/"  rel="nofollow">http://www.mysql.com/products/cluster/</a>

Enjoy !

Changes in MySQL NDB Cluster 8.0.24 (2021-04-20, General Availability)

  MySQL NDB Cluster 8.0.24 is a new release of NDB 8.0, based
  on MySQL Server 8.0 and including features in version 8.0 of
  the NDB storage engine, as well as fixing recently discovered
  bugs in previous NDB Cluster releases.

  Obtaining NDB Cluster 8.0.  NDB Cluster 8.0 source code and
  binaries can be obtained from
  <a href="https://dev.mysql.com/downloads/cluster/"  rel="nofollow">https://dev.mysql.com/downloads/cluster/</a>.

  For an overview of changes made in NDB Cluster 8.0, see What
  is New in NDB Cluster
  (https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-what-is-new.html).

  This release also incorporates all bug fixes and changes made
  in previous NDB Cluster releases, as well as all bug fixes
  and feature changes which were added in mainline MySQL 8.0
  through MySQL 8.0.24 (see Changes in MySQL 8.0.24 (2021-04-20,
  General Availability)
  (https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html)).


Functionality Added or Changed


    * NDB Cluster APIs: The version of Node.js used by NDB has
      been upgraded to 12.20.1. (Bug #32356419)

    * ndbinfo Information Database: Added the dict_obj_tree
      table to the ndbinfo information database. This table
      provides information about NDB database objects similar
      to what is shown by the dict_obj_info table, but presents
      it in a hierarchical or tree-like fashion that simplifies
      seeing relationships between objects such as: tables and
      indexes; tablespaces and data files; log file groups and
      undo log files.
      An example of such a view of a table t1, having a primary
      key on column a and a unique key on column b, is shown
      here:
       mysql&gt; SELECT indented_name FROM ndbinfo.dict_obj_tree
           -&gt; WHERE root_name = &#039;test/def/t1&#039;;
       +----------------------------+
       | indented_name              |
       +----------------------------+
       | test/def/t1                |
       |   -&gt; sys/def/13/b          |
       |     -&gt; NDB$INDEX_15_CUSTOM |
       |   -&gt; sys/def/13/b$unique   |
       |     -&gt; NDB$INDEX_16_UI     |
       |   -&gt; sys/def/13/PRIMARY    |
       |     -&gt; NDB$INDEX_14_CUSTOM |
       +----------------------------+
       7 rows in set (0.15 sec)

      For additional information and examples, see The ndbinfo
      dict_obj_tree Table
      (https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-dict-obj-tree.html).
      (Bug #32198754)

    * ndbinfo Information Database: Added the backup_id table
      to the ndbinfo information database. This table contains
      a single column (id) and a single row, in which the
      column value is the backup ID of the most recent backup
      of the cluster taken with the ndb_mgm client. If no NDB
      backups can be found, the value is 0.
      Selecting from this table replaces the process of
      obtaining this information by using the ndb_select_all
      utility to dump the contents of the internal SYSTAB_0
      table, which is error-prone and can require an
      excessively long time to complete. (Bug #32073640)

    * Added the status variable Ndb_config_generation, which
      shows the generation number of the current configuration
      being used by the cluster. This can be used as an
      indicator to determine whether the configuration of the
      cluster has changed. (Bug #32247424)

    * NDB Cluster now uses the MySQL host_application_signal
      component service to perform shutdown of SQL nodes. (Bug
      #30535835, Bug #32004109)

    * NDB has implemented the following two improvements in
      calculation of index statistics:

         + Previously, index statistics were collected from a
           single fragment only; this is changed such that
           additional fragments are used for these.

         + The algorithm used for very small tables, such as
           those having very few rows where results are
           discarded, has been improved, so that estimates for
           such tables should be more accurate than previously.
      See NDB API Statistics Counters and Variables
      (https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndb-api-statistics.html),
      for more information.

    * A number of NDB Cluster programs now support input of the
      password for encrypting or decrypting an NDB backup from
      standard input. Changes relating to each program affected
      are listed here:

         + For ndb_restore, the --backup-password-from-stdin
           option introduced in this release enables input of
           the password in a secure fashion, similar to how it
           is done by the mysql client&#039; --password option. Use
           this option together with the --decrypt option.

         + ndb_print_backup_file now also supports
           --backup-password-from-stdin as the long form of the
           existing -P option.

         + For ndb_mgm, --backup-password-from-stdin is
           supported together with --execute &quot;START BACKUP
           [options]&quot; for starting an encrypted cluster backup
           from the system shell, and has the same effect.

         + Two options for ndbxfrm,
           --encrypt-password-from-stdin and
           --decrypt-password-from-stdin, which are also
           introduced in this release, cause similar behavior
           when using this program, respectively, to encrypt or
           to decrypt a backup file.
      In addition, you can cause ndb_mgm to use encryption
      whenever it creates a backup by starting it with
      --encrypt-backup. In this case, the user is prompted for
      a password when invoking START BACKUP if none is
      supplied. This option can also be specified in the
      [ndb_mgm] section of the my.cnf file.
      Also, the behavior and syntax of the ndb_mgm management
      client START BACKUP are changed slightly, such that it is
      now possible to use the ENCRYPT option without also
      specifying PASSWORD. Now when the user does this, the
      management client prompts the user for a password.
      For more information, see the descriptions of the NDB
      Cluster programs and program options just mentioned, as
      well as Online Backup of NDB Cluster
      (https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-backup.html).

Bugs Fixed


    * Packaging: RPM upgrades from NDB 7.6.15 to 8.0.22 did not
      succeed due to a file having been moved from the server
      RPM to the client-plugins RPM. (Bug #32208337)

    * Linux: On Linux systems, NDB interpreted memory sizes
      obtained from /proc/meminfo as being supplied in bytes
      rather than kilobytes. (Bug #102505, Bug #32474829)

    * Microsoft Windows: Removed several warnings which were
      generated when building NDB Cluster on Windows using
      Microsoft Visual Studio 2019. (Bug #32107056)

    * Microsoft Windows: NDB failed to start correctly on
      Windows when initializing the NDB library with
      ndb_init(), with the error Failed to find CPU in CPU
      group.
      This issue was due to how Windows works with regard to
      assigning processes to CPUs: when there are more than 64
      logical CPUs on a machine, Windows divides them into
      different processor groups during boot. Each processor
      group can at most hold 64 CPUs; by default, a process can
      be assigned to only one processor group. The function
      std::thread::hardware_concurrency() was used to get the
      maximum number of logical CPUs on the machine, but on
      Windows, this function returns only the maximum number of
      logical CPUs present in the processor group with which
      the current process is affiliated. This value is used to
      allocate memory for an array that holds hardware
      information about each CPU on the machine. Since the
      array held valid memory for CPUs from only one processor
      group, any attempt to store and retrieve hardware
      information about a CPU in a different processor group
      led to array bound read/write errors, leading to memory
      corruption and ultimately leads to process failures.
      Fixed by using GetActiveProcessorCount() instead of the
      hardware_concurrency() function referenced previously.
      (Bug #101347, Bug #32074703)

    * Solaris: While preparing NDBFS for handling of encrypted
      backups, activation of O_DIRECT was suspended until after
      initialization of files was completed. This caused
      initialization of redo log files to require an excessive
      amount of time on systems using hard disk drives with
      ext3 file systems.
      On Solaris, directio is used instead of O_DIRECT;
      activating directio prior to initialization of files
      caused a notable increase in time required when using
      hard disk drives with UFS file systems.
      Now we ensure that, on systems having O_DIRECT, this is
      activated before initialization of files, and that, on
      Solaris, directio continues to be activated after
      initialization of files. (Bug #32187942)

    * NDB Cluster APIs: Several NDB API coding examples
      included in the source did not release all resources
      allocated. (Bug #31987735)

    * NDB Cluster APIs: Some internal dictionary objects in NDB
      used an internal name format which depends on the
      database name of the Ndb object. This dependency has been
      made more explicit where necessary and otherwise removed.
      Users of the NDB API should be aware that the
      fullyQualified argument to Dictionary::listObjects()
      still works in such a way that specifying it as false
      causes the objects in the list it returns to use fully
      qualified names. (Bug #31924949)

    * ndbinfo Information Database: The system variables
      ndbinfo_database and ndbinfo_table_prefix are intended to
      be read-only. It was found that it was possible to set
      mysqld command-line options corresponding to either or
      both of these; doing so caused the ndbinfo database to
      malfunction. This fix insures that it is no longer
      possible to set either of these variables in the mysql
      client or from the command line. (Bug #23583256)

    * In some cases, a query affecting a user with the
      NDB_STORED_USER privilege could be printed to the MySQL
      server log without being rewritten. Now such queries are
      omitted or rewritten to remove any text following the
      keyword IDENTIFIED. (Bug #32541096)

    * The value set for the SpinMethod data node configuration
      parameter was ignored. (Bug #32478388)

    * The compile-time debug flag DEBUG_FRAGMENT_LOCK was
      enabled by default. This caused increased resource usage
      by DBLQH, even for release builds.
      This is fixed by disabling DEBUG_FRAGMENT_LOCK by
      default. (Bug #32459625)

    * ndb_mgmd now exits gracefully in the event of a SIGTERM
      just as it does following a management client SHUTDOWN
      command. (Bug #32446105)

    * When started on a port which was already in use, ndb_mgmd
      did not throw any errors since the use of SO_REUSEADDR on
      Windows platforms allowed multiple sockets to bind to the
      same address and port.
      To take care of this issue, we replace SO_REUSEADDRPORT
      with SO_EXCLUSIVEADDRUSE, which prevents re-use of a port
      that is already in use. (Bug #32433002)

    * Encountering an error in detection of an initial system
      restart of the cluster caused the SQL node to exit
      prematurely. (Bug #32424580)

    * The values reported for the to and from arguments in job
      buffer full issues were reversed. (Bug #32413686)

    * Under some situations, when trying to measure the time of
      a CPU pause, an elapsed time of zero could result. In
      addition, computing the average for a very fast spin (for
      example, 100 loops taking less than 100ns) could zero
      nanoseconds. In both cases, this caused the spin
      calibration algorithm throw an arithmetic exception due
      to division by zero.
      We fix both issues by modifying the algorithm so that it
      ignores zero values when computing mean spin time. (Bug
      #32413458)
      References: See also: Bug #32497174.

    * Table and database names were not formatted correctly in
      the messages written to the mysqld error log when the
      internal method Ndb_rep_tab_reader::scan_candidates()
      found ambiguous matches for a given database, table, or
      server ID in the ndb_replication table. (Bug #32393245)

    * Some queries with nested pushed joins were not processed
      correctly. (Bug #32354817)

    * When ndb_mgmd allocates a node ID, it reads through the
      configuration to find a suitable ID, causing a mutex to
      be held while performing hostname lookups. Because
      network address resolution can require large amounts of
      time, it is not considered good practice to hold such a
      mutex or lock while performing network operations.
      This issue is fixed by building a list of configured
      nodes while holding the mutex, then using the list to
      perform hostname matching and other logic. (Bug
      #32294679)

    * The schema distribution participant failed to start a
      global checkpoint after writing a reply to the
      ndb_schema_result table, which caused an unnecessary
      delay before the coordinator received events from the
      participant notifying it of the result. (Bug #32284873)

    * The global DNS cache used in ndb_mgmd caused stale
      lookups when restarting a node on a new machine with a
      new IP address, which meant that the node could not
      allocate a node ID.
      This issue is addressed by the following changes:

         + Node ID allocation no longer depends on
           LocalDnsCache

         + DnsCache now uses local scope only
      (Bug #32264914)

    * ndb_restore generated a core file when started with
      unknown or invalid arguments. (Bug #32257374)

    * Auto-synchronization detected the presence of mock
      foreign key tables in the NDB dictionary and attempted to
      re-create them in the MySQL server&#039;s data dictionary,
      although these should remain internal to the NDB
      Dictionary and not be exposed to the MySQL server. To fix
      this issue, we now ensure that the NDB Cluster
      auto-synchronization mechanism ignores any such mock
      tables. (Bug #32245636)

    * Improved resource usage associated with handling of
      cluster configuration data. (Bug #32224672)

    * Removed left-over debugging printouts from ndb_mgmd
      showing a client&#039;s version number upon connection. (Bug
      #32210216)
      References: This issue is a regression of: Bug #30599413.

    * While retrieving sorted results from a pushed-down join
      using ORDER BY with the index access method (and without
      filesort), an SQL node sometimes unexpectedly terminated.
      (Bug #32203548)

    * Logging of redo log initialization showed log part
      indexes rather than log part numbers. (Bug #32200635)

    * Signal data was overwritten (and lost) due to use of
      extended signal memory as temporary storage. Now in such
      cases, extended signal memory is not used in this
      fashion. (Bug #32195561)

    * When ClassicFragmentation = 1, the default number of
      partitions per node (shown in ndb_desc output as
      PartitionCount) is calculated using the lowest number of
      LDM threads employed by any single live node, and was
      done only once, even after data nodes left or joined the
      cluster, possibly with a new configuration changing the
      LDM thread count and thus the default partition count.
      Now in such cases, we make sure the default number of
      partitions per node is recalculated each time data nodes
      join or leave the cluster.
      This is not an issue in NDB 8.0.23 and later, when
      ClassicFragmentation is set to 0. (Bug #32183985)

    * The internal function Ndb_ReloadHWInfo() is responsible
      for updating hardware information for all the CPUs on the
      host. For the Linux ARM platform, which does not have
      Level 3 cache information, this assigned a socket ID for
      the L3 cache ID but failed to record the value for the
      global variable num_shared_l3_caches, which is needed
      when creating lists of CPUs connected to a shared L3
      cache. (Bug #32180383)

    * When trying to run two management nodes on the same host
      and using the same port number, it was not always obvious
      to users why they did not start. Now in such cases, in
      addition to writing a message to the error log, an error
      message Same port number is specified for management
      nodes node_id1 and node_id2 (or) they both are using the
      default port number on same host host_name is also
      written to the console, making the source of the issue
      more immediately apparent. (Bug #32175157)

    * Added a --cluster-config-suffix option for ndb_mgmd and
      ndb_config, for use in internal testing to override a
      defaults group suffix. (Bug #32157276)

    * The management server returned the wrong status for host
      name matching when some of the host names in
      configuration did not resolve and client trying to
      allocate a node ID connected from the host whose host
      name resolved to a loopback address with the error Could
      not alloc node id at &lt;host&gt;:&lt;port&gt;: Connection with id X
      done from wrong host ip 127.0.0.1, expected
      &lt;unresolvable_host&gt; (lookup failed).
      This caused the connecting client to fail the node ID
      allocation.
      This issue is fixed by rewriting the internal
      match_hostname() function so that it contains all logic
      for how the requesting client address should match the
      configured hostnames, and so that it first checks whether
      the configured host name can be resolved; if not, it now
      returns a special error so that the client receives an
      error indicating that node ID allocation can be retried.
      The new error is Could not alloc node id at
      &lt;host&gt;:&lt;port&gt;: No configured host found of node type
      &lt;type&gt; for connection from ip 127.0.0.1. Some hostnames
      are currently unresolvable. Can be retried. (Bug
      #32136993)

    * The internal function ndb_socket_create_dual_stack() did
      not close a newly created socket when a call to
      ndb_setsockopt() was unsuccessful. (Bug #32105957)

    * The local checkpoint (LCP) mechanism was changed in NDB
      7.6 such that it also detected idle fragments---that is,
      fragments which had not changed since the last LCP and
      thus required no on-disk metadata update. The LCP
      mechanism could then immediately proceed to handle the
      next fragment. When there were a great many such idle
      fragments, the CPU consumption required merely to loop
      through these became highly significant, causing latency
      spikes in user transactions.
      A 1 ms delay was already inserted between each such idle
      fragment being handled. Testing later showed this to be
      too short an interval, and that we are normally not in as
      great a hurry to complete these idle fragments as we
      previously believed.
      This fix extends the idle fragment delay time to 20 ms if
      there are no redo alerts indicating an urgent need to
      complete the LCP. In case of a low redo alert state we
      wait 5 ms instead, and for a higher alert state we fall
      back to the 1 ms delay. (Bug #32068551)
      References: See also: Bug #31655158, Bug #31613158.

    * When an NDB table was created, it was invalidated in the
      global dictionary cache, but this was unnecessary.
      Furthermore, having a table which exists in the global
      dictionary cache is actually an advantage for subsequent
      uses of the new table, since it can be found in the table
      cache without performing a round trip to NDB. (Bug
      #32047456)

    * No clear error message was provided when an mgmd process
      tried to start using the PortNumber of a port that was
      already in use. (Bug #32045786)

    * Two problems occurred when NDB closed a table:

         + NDB failed to detect when the close was done from
           FLUSH TABLES, which meant that the NDB table
           definitions in the global dictionary cache were not
           invalidated.

         + When the close was done by a thread which had not
           used NDB earlier---for example when FLUSH TABLES or
           RESET MASTER closed instances of ha_ndbcluster held
           in the table definition cache---a new Thd_ndb object
           was allocated, even though there is a fallback to
           the global Ndb object in case the allocation fails,
           which never occurs in such cases, so it is less
           wasteful simply to use the global object already
           provided.
      (Bug #32018394, Bug #32357856)

    * Removed a large number of compiler warnings relating to
      unused function arguments in NdbDictionaryImpl. (Bug
      #31960757)

    * Unnecessary casts were performed when checking internal
      error codes. (Bug #31930166)

    * NDB continued to use file system paths for determining
      the names of tables to open or perform DDL on, in spite
      of the fact that it longer actually uses files for these
      operations. This required unnecessary translation between
      character sets, handling the MySQL-specific file system
      encoding, and parsing. In addition, results of these
      operations were stored in buffers of fixed size, each
      instance of which used several hundred bytes of memory
      unnecessarily. Since the database and table names to use
      are already available to NDB through other means, this
      translation could be (and has been) removed in most
      cases. (Bug #31846478)

    * Generation of internal statistics relating to NDB object
      counts was found to lead to an increase in transaction
      latency at very high rates of transactions per second,
      brought about by returning an excessive number of freed
      NDB objects. (Bug #31790329)

    * NDB behaved unpredictably in response an attempt to
      change permissions on a distributed user (that is, a user
      having the NDB_STORED_USER privilege) during a binary log
      thread shutdown and restart. We address this issue by
      ensuring that the user gets a clear warning Could not
      distribute ACL change to other MySQL servers whenever
      distribution does not succeed. This fix also improves a
      number of mysqld log messages. (Bug #31680765)

    * ndb_restore encountered intermittent errors while
      replaying backup logs which deleted blob values; this was
      due to deletion of blob parts when a main table row
      containing blob one or more values was deleted. This is
      fixed by modifying ndb_restore to use the asynchronous
      API for blob deletes, which does not trigger blob part
      deletes when a blob main table row is deleted (unlike the
      synchronous API), so that a delete log event for the main
      table deletes only the row from the main table. (Bug
      #31546136)

    * Upgrading to NDB Cluster 8.0 from a prior release
      includes an upgrade in the schema distribution mechanism,
      as part of which the ndb_schema table is dropped and
      recreated in a way which causes all MySQL Servers
      connected to the cluster to restart their binary log
      injector threads, causing a gap event to be written to
      the binary log. Since the thread restart happens at the
      same time on all MySQL Servers, no binary log spans the
      time during which the schema distribution functionality
      upgrade was performed, which breaks NDB Cluster
      Replication.
      This issue is fixed by adding support for gracefully
      reconstituting the schema distribution tables while
      allowing the injector thread to continue processing
      changes from the cluster. This is implemented by handling
      the DDL event notification for DROP TABLE to turn off
      support for schema distribution temporarily, and to start
      regular checks to re-create the tables. When the tables
      have been successfully created again, the regular checks
      are turned off and support for schema distribution is
      turned back on.
      In addition, the minimum version required to perform the
      schema distribution upgrade is raised to 8.0.24, which
      prevents automatic triggering of the schema distribution
      upgrade until all connected API nodes support the new
      upgrade procedure. (Bug #30877233)
      References: See also: Bug #30876990.

    * When a table creation schema transaction is prepared, the
      table is in TS_CREATING state, and is changed to
      TS_ACTIVE state when the schema transaction commits on
      the DBDIH block. In the case where the node acting as
      DBDIH coordinator fails while the schema transaction is
      committing, another node starts taking over for the
      coordinator. The following actions are taken when
      handling this node failure:

         + DBDICT rolls the table creation schema transaction
           forward and commits, resulting in the table involved
           changing to TS_ACTIVE state.

         + DBDIH starts removing the failed node from tables by
           moving active table replicas on the failed node from
           a list of stored fragment replicas to another list.
      These actions are performed asynchronously many times,
      and when interleaving may cause a race condition. As a
      result, the replica list in which the replica of a failed
      node resides becomes nondeterministic and may differ
      between the recovering node (that is, the new
      coordinator) and other DIH participant nodes. This
      difference violated a requirement for knowing which list
      the failed node&#039;s replicas can be found during the
      recovery of the failed node recovery on the other
      participants.
      To fix this, moving active table replicas now covers not
      only tables in TS_ACTIVE state, but those in TS_CREATING
      (prepared) state as well, since the prepared schema
      transaction is always rolled forward.
      In addition, the state of a table creation schema
      transaction which is being aborted is now changed from
      TS_CREATING or TS_IDLE to TS_DROPPING, to avoid any race
      condition there. (Bug #30521812)

    * START BACKUP SNAPSHOTSTART WAIT STARTED could return
      control to the user prior to the backup&#039;s restore point
      from the user point of view; that is the Backup started
      notification was sent before waiting for the
      synchronising global checkpoint (GCP) boundary. This
      meant that transactions committed after receiving the
      notification might be included in the restored data.
      To fix this problem, START BACKUP now sends a
      notification to the client that the backup has been
      started only after the GCP has truly started. (Bug
      #29344262)

    * Fixed a number of issues uncovered when trying to build
      NDB with GCC 6. (Bug #25038373)

    * Calculation of the redo alert state based on redo log
      usage was overly aggressive, and thus incorrect, when
      using more than 1 log part per LDM.

On Behalf of the MySQL Engineering Team,
Hery Ramilison 
</pre>]]></description>
            <dc:creator>Hery Ramilison</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 15:27:04 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696006,696006#msg-696006</guid>
            <title>MySQL Connector/J 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696006,696006#msg-696006</link>
            <description><![CDATA[ <pre class="bbcode">

Dear MySQL users,

MySQL Connector/J 8.0.24 is the latest General Availability release of the
MySQL Connector/J 8.0 series.  It is suitable for use with MySQL Server
versions 8.0 and 5.7.  It supports the Java Database Connectivity (JDBC)
4.2 API, and implements the X DevAPI.

This release includes the following new features and changes, also described in
more detail on

<a href="https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-24.html"  rel="nofollow">https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-24.html</a>

As always, we recommend that you check the &quot;CHANGES&quot; file in the download
archive to be aware of changes in behavior that might affect your application.

To download MySQL Connector/J 8.0.24 GA, see the &quot;General Availability (GA)
Releases&quot; tab at <a href="http://dev.mysql.com/downloads/connector/j/"  rel="nofollow">http://dev.mysql.com/downloads/connector/j/</a>

Enjoy!

Changes in MySQL Connector/J 8.0.24 (2021-04-20, General Availability)

     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


     * X DevAPI: For X Protocol connections, the Server now
       provides three new kinds of notifications for
       disconnections:

          + Server shutdown: This is due to a server shutdown.
            It causes Connector/J to terminate all active and
            idle sessions connected to the server in the
            connection pool with the error message &quot;Server
            shutdown in progress&quot;.

          + Connection idle: This is due to the connection
            idling for longer than the relevant timeout
            settings. It causes Connector/J to close the current
            connection with the error message &quot;IO Read error:
            read_timeout exceeded&quot;.

          + Connection killed: This is due to the connection
            being killed by another client session. It causes
            Connector/J to close the connection in the current
            session with the error message &quot;Session was killed&quot;.

     * A new connection property, scrollTolerantForwardOnly, has
       been introduced, which preserved the legacy behavior of
       Connector/J 8.0.17 and earlier by tolerating backward and
       absolute cursor movements on result sets of type
       ResultSet.TYPE_FORWARD_ONLY. This is for maintaining
       compatibility with legacy code that took advantage of the
       old behavior. See the description for
       scrollTolerantForwardOnly for details. (Bug #31747910)
       References: See also: Bug #30474158.

     * Connector/J now supports &quot;userless&quot; authentication for
       JDBC connections: When the user for the connection is
       unspecified, Connector/J uses the name of the OS user who
       runs the application for authentication with the MySQL
       server. See Connector/J: Obtaining a connection from the
       DriverManager
(https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-connect-drivermanager.html#connector-j-examples-connection-drivermanager)
       for more details.

     * Starting from this release, whenever an authentication
       plugin is explicitly set for the connection property
       defaultAuthenticationPlugin
(https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-connp-props-connection.html#cj-conn-prop_defaultAuthenticationPlugin),
       the specified plugin takes precedence over
       the server&#039;s default when Connector/J negotiates a plugin
       with the server. There is no behavioral change for
       Connector/J if no value is explicitly set for the
       property, in which case the server&#039;s choice of default
       plugin takes precedence over the implicit default of
       mysql_native_password for Connector/J. See the
       description of defaultAuthenticationPlugin
(https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-connp-props-connection.html#cj-conn-prop_defaultAuthenticationPlugin)
       for details.

     * In the past, for JDBC connections, when the server closed
       a session because a client was idling beyond the period
       specified by the server&#039;s wait_timeout system variable,
       Connector/J returned a generic IO error. Connector/J now
       relays a clearer error message from the server.

Bugs Fixed


     * X DevAPI: Concurrently getting and closing multiple
       sessions from the same X DevAPI Client object might
       result in a ConcurrentModificationException thrown by
       Connector/J at the closing of a session. (Bug #31699993)

     * X DevAPI: Under some specific conditions, when using
       Deflate as the algorithm for compression of X Protocol
       connections, Connector/J threw an
       AssertionFailedException (ASSERTION FAILED: Unknown
       message type: 57). It was because when a compressed
       packet was just a few bytes longer than the size of some
       internal buffer used by a Java InflaterInputStream, the
       leftover bytes from the inflate procedure were being
       discarded by Connector/J, causing inflation of subsequent packets
       to fail. With this fix, no data bytes are discarded, and
       the inflation works as expected. (Bug #31510398, Bug
       #99708)

     * When a SecurityManager was in place, connections to a
       MySQL Server could not be established unless the client
       had been properly configured to use SASL-based LDAP
       authentication. It was because the
       AuthenticationLdapSaslClientPlugin in Connector/J
       requires a special permission to load the provider
       MySQLScramShaSasl when a SecurityManager is in place; but
       since the provider was loaded by a static initializer
       during initialization for the plugin, the lack of the
       permission was causing an error and then failures for all
       connections, even if the plugin was never used or
       enabled. This fix changes how the provider is loaded: the
       loading now happens only at the plugin instance&#039;s
       initialization and the initialization was deferred to the
       time when the plugin is actually needed, so that
       connections that do not use SASL-based LDAP
       authentication are unaffected by security settings
       regarding the plugin. (Bug #32526663, Bug #102188)

     * When using Connector/J 8.0.23,
       ResultSetMetaData.getColumnClassName() did not return the
       correct class name corresponding to DATETIME columns.
       (Bug #32405590, Bug #102321)

     * Creation of an UpdatableResultSet failed with a
       NullPointerException when it was generated by querying a
       view with a derived value. (Bug #32338451, Bug #102131)

     * Using getLong() on the CHAR_OCTET_LENGTH column of the
       ResultSet for DatabaseMetaData.getProcedureColumns() (or
       getFunctionColumns()) resulted in a NumberOutOfRange
       exception when the column&#039;s value exceeded 2^32 − 1. With
       this patch, the value of 2^32 − 1 is returned in the
       situation. (Bug #32329915, Bug #102076)

     * Connections to a server could not be established when the
       user supplied an implementation of the
       ConnectionPropertiesTransform interface using the
       connection property propertiesTransform. This was because
       Connector/J called PropertyKey.PORT.getKeyName() instead
       of PropertyKey.HOST.getKeyName() for getting the host
       name, and that has been corrected by this fix. (Bug
       #32151143, Bug #101596)

     * A NullPointerException was returned when a statement that
       could not be used as a ServerPreparedStatement was
       executed and the connection property useUsageAdvisor
(https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-connp-props-debugging-profiling.html#cj-conn-prop_useUsageAdvisor)
       was set to true. With this fix, a SQLException
       is returned instead. (Bug #32141210, Bug #101558)

     * Using the setSessionMaxRows() method on a closed
       connection resulted in a NullPointerException. With this
       fix, a SQLNonTransientConnectionException is thrown
       instead, with the error message &quot;No operations allowed
       after connection closed.&quot; (Bug #22508715)

     * Using the setObject() method for a target type of
       Types.TIME resulted in a SQLException when the value to
       be set had a fractional part, or when the value did not
       fit any pattern described in Date and Time Literals
(https://dev.mysql.com/doc/refman/8.0/en/date-and-time-literals.html).
       This patch introduced a new logic that can
       handle fractional parts; also, it performs the conversion
       according to the patterns of the literals and, when
       needed, the target data type. (Bug #20391832)

Enjoy and thanks for the support!

On Behalf of the MySQL Engineering Team,
Nawaz Nazeer Ahamed
</pre>]]></description>
            <dc:creator>Nawaz Nazeer Ahamed</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 13:04:51 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696005,696005#msg-696005</guid>
            <title>MySQL Shell 8.0.24 for MySQL Server 8.0 and 5.7 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696005,696005#msg-696005</link>
            <description><![CDATA[ <pre class="bbcode">

Dear MySQL users,

MySQL Shell 8.0.24 is a maintenance release of MySQL Shell 8.0 Series (a
component of the MySQL Server). The MySQL Shell is provided under Oracle&#039;s
dual-license.

MySQL Shell 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7.
Please upgrade to MySQL Shell 8.0.24.

MySQL Shell is an interactive JavaScript, Python and SQL console interface,
supporting development and administration for the MySQL Server. It provides
APIs implemented in JavaScript and Python that enable you to work with MySQL
InnoDB Cluster and use MySQL as a document store.

The AdminAPI enables you to work with MySQL InnoDB Cluster and InnoDB
ReplicaSet, providing integrated solutions for high availability and
scalability using InnoDB based MySQL databases, without requiring advanced
MySQL expertise.  For more information about how to configure and work with
MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet see

<a href="https://dev.mysql.com/doc/mysql-shell/8.0/en/admin-api-userguide.html"  rel="nofollow">https://dev.mysql.com/doc/mysql-shell/8.0/en/admin-api-userguide.html</a>

The X DevAPI enables you to create &quot;schema-less&quot; JSON document collections and
perform Create, Update, Read, Delete (CRUD) operations on those collections
from your favorite scripting language.  For more information about how to use
MySQL Shell and the MySQL Document Store support see

<a href="https://dev.mysql.com/doc/refman/en/document-store.html"  rel="nofollow">https://dev.mysql.com/doc/refman/en/document-store.html</a>

For more information about the X DevAPI see

<a href="https://dev.mysql.com/doc/x-devapi-userguide/en/"  rel="nofollow">https://dev.mysql.com/doc/x-devapi-userguide/en/</a>

If you want to write applications that use the the CRUD based X DevAPI you can
also use the latest MySQL Connectors for your language of choice. For more
information about Connectors see

<a href="https://dev.mysql.com/doc/index-connectors.html"  rel="nofollow">https://dev.mysql.com/doc/index-connectors.html</a>

For more information on the APIs provided with MySQL Shell see

<a href="https://dev.mysql.com/doc/dev/mysqlsh-api-javascript/8.0/"  rel="nofollow">https://dev.mysql.com/doc/dev/mysqlsh-api-javascript/8.0/</a>

and

<a href="https://dev.mysql.com/doc/dev/mysqlsh-api-python/8.0/"  rel="nofollow">https://dev.mysql.com/doc/dev/mysqlsh-api-python/8.0/</a>

Using MySQL Shell&#039;s SQL mode you can communicate with servers using the legacy
MySQL protocol. Additionally, MySQL Shell provides partial compatibility with
the mysql client by supporting many of the same command line options.

For full documentation on MySQL Server, MySQL Shell and related topics, see

<a href="https://dev.mysql.com/doc/mysql-shell/8.0/en/"  rel="nofollow">https://dev.mysql.com/doc/mysql-shell/8.0/en/</a>

For more information about how to download MySQL Shell 8.0.24, see the &quot;General
Availability (GA) Releases&quot; tab at

<a href="http://dev.mysql.com/downloads/shell/"  rel="nofollow">http://dev.mysql.com/downloads/shell/</a>

We welcome and appreciate your feedback and bug reports, see

<a href="http://bugs.mysql.com/"  rel="nofollow">http://bugs.mysql.com/</a>

Enjoy!

Changes in MySQL Shell 8.0.24 (2021-04-20, General Availability)


     * AdminAPI Added or Changed Functionality

     * AdminAPI Bugs Fixed

     * Functionality Added or Changed

     * Bugs Fixed

AdminAPI Added or Changed Functionality


     * The API command-line integration, used for scripting
       MySQL Shell, has been improved to use the function and
       option metadata to properly parse arguments and associate
       them to the corresponding parameter in the API call.
       Previously, the command-line integration was processing
       all the arguments as strings, causing errors using
       operations such as:
&gt; mysqlsh user@hostname:3306 -- cluster setOption &quot;autoRejoinTries&quot;  5
       The command-line integration now interprets the data
       being passed in based on what the API functions expect to
       receive. This enhancement also introduces support for
       lists in command-line integration calls.
       Additionally, you can now access the MySQL Shell online
       help from the command-line integration. For example, to
       get help on the shell.options functions, issue:
$ mysqlsh -- shell options --help

       For more information, see API Command Line Integration
(https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-command-line-integration.html).
       In addition, when registering a new MySQL Shell extension
       function, the new boolean cli option is supported by the
       shell.addExtensionObjectMember() operation. When an
       operation is registered with the cli option set to true,
       the object and the functions are made available for the
       command-line integration. This enables you to extend the
       scripting possibilities of MySQL Shell. (Bug #31186637)

AdminAPI Bugs Fixed


     * Most of the AdminAPI operations contain metadata
       preconditions to determine if it is valid or not to
       execute them. When this check was being done, it was
       adding two entries to the log, one to indicate the check
       was about to be done, and another to indicate the
       metadata state. This meant that operations such as
       monitoring a cluster, which implies executing regular
       status requests, resulted in a large number of log
       entries. Now, these two log messages have been merged
       into a single entry that gets logged at the info level
       when the metadata state is not correct, and as debug info
       when the state is correct. In other words, if the
       metadata state is correct, the message is only logged
       when log_level=debug. (Bug #32582745)

     * The memberRole is now included in the default output of
       Cluster.status(). Previously, this information was only
       included when the extended option had a value of 1 or
       higher. This makes it easier to know what an instance&#039;s
       role is in the cluster, regardless of whether its
       operating mode is R/W or R/O. (Bug #32381513)

     * dba.checkInstanceConfiguration() was performing an
       incorrect validation regarding the required privileges.
       This resulted in an endless loop where the operation
       detected missing privileges, you would give the grants as
       specified by the interactive help, but the operation
       would fail, indicating that the grants were missing. Now,
       the verification checks the correct list. Additionally,
       the internal list of required grants included SUPER,
       which is deprecated in 8.0. The fix replaces the SUPER
       grant with the fine-grained grants. (Bug #32287986)

     * The memberSslMode option did not support the VERIFY_CA
       and VERIFY_IDENTITY modes for the following operations:

          + dba.createCluster()

          + Cluster.addInstance()

          + Cluster.rejoinInstance()
       Now, the memberSslMode option supports these modes, and
       when they are used there is a validation to ensure that
       the CA certificates are supplied. If you choose to use
       the VERIFY_CA or VERIFY_IDENTITY mode, on each cluster
       instance you must manually supply the CA certificates
       using the ssl_ca and/or ssl_capath option. For more
       information, see Securing your Cluster
(https://dev.mysql.com/doc/mysql-shell/8.0/en/configuring-innodb-cluster.html#mysql-innodb-cluster-securing).
       Thanks to Daniël van Eeden for the contribution. (Bug
       #32247631, Bug #32241000)

     * In version 8.0.23, a check was added to verify if the
       server_id of all cluster instances is registered in the
       metadata as an instance attribute, and if not then the
       metadata is updated accordingly. This check is executed
       on add, rejoin and rescan operations. However, when
       upgrading a cluster from a version earlier than 8.0.23 to
       version 8.0.23 and higher, the server_id was not
       registered in the metadata unless you performed a manual
       rejoin. This was being silently ignored because it was
       not included in any diagnostic messages. Now, a new
       verification checks if the server_id of cluster instances
       is missing from the metadata and includes a note message
       in the instanceErrors attribute in the output of
       Cluster.status() indicating to use Cluster.rescan() to
       fix it. (Bug #32226871)

     * From MySQL Shell version 8.0.17, AdminAPI stores the
       replication or recovery accounts used for each added
       instance in the metadata schema, in the instances table.
       However, the specific transaction could fail or that
       entry might have been manually removed from the metadata
       schema, resulting in failures when trying to add other
       instances to the cluster, and there was no way to resolve
       this using AdminAPI. In such a situation, if you tried to
       add an instance the operation failed with an error. Now,
       AdminAPI tries to detect problems in the metadata related
       to these accounts for an InnoDB Cluster or InnoDB
       ReplicaSet. The status() operation prints a message if
       the required account is missing in the metadata schema,
       and also if it is not the one actually used. In such
       situations, the MySQL Shell help instructs you to either
       re-add the instance or run rescan() based on the detected
       problem. The addInstance() operation also prints a hint
       to call rescan() if any missing recovery users are found
       in the metadata. (Bug #32157182)

     * Cluster.addInstance() was permitting usage of the
       expelTimeout and consistency options when it should not.
       These options are cluster level settings that can only be
       set using dba.createCluster() and Cluster.setOption().
       (Bug #29779995)

     * The dba.checkInstanceConfiguration() operation detects if
       the instance has any tables that do not have a primary
       key. Group Replication requires every table that is to be
       replicated by the group to have a defined primary key.
       However, this does not mean that having a table without a
       primary key causes Group Replication to block or fail.
       Rather, the outcome is that changes to that table are not
       replicated but the group continues operating. Previously,
       if the dba.checkInstanceConfiguration() operation
       detected a table without a primary key, the operation
       returned with a status of ok and only mentioned tables
       with a missing primary key and unsupported engines. Now,
       if the operation detects such a table, it returns with a
       status of error. As part of this work, the
       dba.createCluster() operation has been changed to fail if
       it finds such tables. (Bug #29771457)

     * As part of the fix for Bug#28701263, AdminAPI started
       setting and persisting a default value of READ_ONLY for
       the group_replication_exit_state_action system variable.
       The default used by Group Replication was ABORT_SERVER.
       However, in MySQL Server 8.0.16 the default value of
       group_replication_exit_state_action became READ_ONLY so
       AdminAPI should not change and persist it. Now, on
       instances running 8.0.16 and later, the value of
       group_replication_exit_state_action is not modified. (Bug
       #29037274)

     * The exception information listed in the online help had
       become outdated and unwieldy for the interactive MySQL
       Shell, so it has been removed. (Bug #28542904)
       References: See also: Bug #29853828, Bug #32426083, Bug
       #32157120, Bug #28825389.

     * Using the allowRootFrom option with the
       dba.deploySandboxInstance() operation was creating a
       different remote root account depending on whether MySQL
       Shell was running in interactive mode or not. Now, the
       default value of allowRootFrom is consistent between both
       modes, and the account is created as root@% in both
       interactive and non-interactive mode. (Bug #27369121)

     * When you issue dba.createCluster() and
       dba.createReplica(), tables are created to store the
       metadata. If the default storage engine was not InnoDB,
       these operations could fail. Now, metadata creation
       operations always use the InnoDB storage engine. (Bug
       #101446, Bug #32110085)

Functionality Added or Changed


     * From MySQL 8.0.24, SQL statements that you issue in MySQL
       Shell&#039;s SQL mode can be sent to the operating system&#039;s
       system logging facility (syslog on Unix, or the Windows
       Event Log). You can select this option by specifying the
       --syslog command-line option when starting MySQL Shell,
       or by setting the history.sql.syslog MySQL Shell
       configuration option. SQL statements that would be
       excluded from the MySQL Shell code history are also
       excluded from the system logging facility. (Bug
       #31995742, Bug #31514599)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance(),
       schema dump utility util.dumpSchemas(), and table dump
       utility util.dumpTables() can now check for tables that
       do not contain primary keys. The check is carried out
       when the ocimds option is enabled for checking
       compatibility with MySQL Database Service, and an error
       is reported for every table included in the dump that
       does not have a primary key. The compatibility option,
       which implements appropriate measures for compatibility,
       has two new modification choices to notify MySQL Shell&#039;s
       dump loading utility to create primary keys in invisible
       columns for tables that do not have them, or to ignore
       the missing primary keys. Primary keys are required for
       MySQL Database Service High Availability, which uses
       Group Replication.

Bugs Fixed


     * Previously, MySQL Shell retried requests to Oracle Cloud
       Infrastructure Object Storage a maximum of 5 times, with
       a 30 second wait in between retries, and a maximum
       overall wait of 5 minutes. The retry strategy has now
       been changed to increase the wait window and reduce the
       possibility of a dump or load operation failing. MySQL
       Shell now retries a maximum of 10 times, with a 1 minute
       wait in between retries, and a maximum overall wait of 10
       minutes. (Bug #32592962)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance()
       stopped with an error if the last schema to be dumped was
       a schema that contained no tables. The issue has now been
       fixed. (Bug #32540460)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance()
       has been optimized so that it can still be used
       successfully if there are limitations on the server&#039;s
       resources such as disk space or the thread stack. To
       handle such situations, the queries from the utility can
       be repeated to retrieve smaller chunks of data if
       required, and file sorting is avoided. (Bug #32528186)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance()
       incorrectly removed grants of all privileges to users.
       The utility now expands GRANT ALL statements in the dump
       to list all privileges granted on all schemas and tables
       (*.*), and to list allowed privileges for system schemas.
       The dump loading utility util.loadDump() now extracts the
       lists of allowed and revoked global privileges during
       loading, and strips these from GRANT statements relating
       to system schemas and to all schemas and tables. (Bug
       #32526567)

     * MySQL Shell&#039;s dump loading utility util.loadDump() now
       grants privileges after all the data is loaded.
       Previously, an error could occur if the utility tried to
       grant a privilege on a routine that did not yet exist.
       (Bug #32526496)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance(),
       schema dump utility util.dumpSchemas(), and table dump
       utility util.dumpTables() could not complete the dump if
       the gtid_executed system variable or the Information
       Schema&#039;s COLUMN_STATISTICS table was unavailable. The
       utilities now display a warning message and log a
       detailed error message in this situation. These items are
       not required for a successful dump. (Bug #32515696)

     * MySQL Shell&#039;s handling and formatting has been improved
       for the help text that you provide for dictionary
       parameters and their options when you register a Python
       plugin. (Bug #32509309)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance(),
       schema dump utility util.dumpSchemas(), and table dump
       utility util.dumpTables() no longer write a FLUSH TABLES
       statement to the binary log, as this can interfere with
       replication. (Bug #32490714)

     * From MySQL 8.0.23, MySQL Server supports replication from
       a source server that does not have GTIDs enabled and does
       not use GTID-based replication, to a replica that has
       GTIDs enabled, using the
       ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS option of the
       CHANGE REPLICATION SOURCE TO statement. MySQL Shell&#039;s
       instance dump utility util.dumpInstance(), schema dump
       utility util.dumpSchemas(), and table dump utility
       util.dumpTables() now support this functionality by
       storing the binary log file name and position in the dump
       metadata, in addition to the gtid_executed GTID set. The
       additional privilege REPLICATION CLIENT is required in
       order for the utilities to be able to collect this
       information, although if the user ID does not have that
       privilege, the dump continues but without the binary log
       information.
       The binary log information can be used after loading the
       dumped data into the replica server to set up replication
       with a non-GTID source server. MySQL Shell&#039;s dump loading
       utility util.loadDump() prints the binary log and GTID
       set information from the dump metadata (in YAML format)
       when you specify the new option showMetadata: true. (Bug
       #32430402)

     * MySQL Shell did not correctly handle an empty array that
       was added to a collection. The result set normally
       returned from the server is now skipped in this
       situation. (Bug #32377134)

     * MySQL Shell&#039;s instance dump utility util.dumpInstance(),
       schema dump utility util.dumpSchemas(), and table dump
       utility util.dumpTables() were unable to chunk table data
       from a MySQL 5.6 server instance, due to differences in
       the output of the EXPLAIN SELECT statement for that
       version. The utilities now account for the difference,
       and also cache the server version information for faster
       access. (Bug #32376447)

     * MySQL Shell&#039;s parallel table import utility
       util.importTable() set a zero exit code if a non-critical
       error occurred that did not interrupt the import, such as
       a directory or file not being found. The utility now sets
       a non-zero error code instead when the first non-critical
       error is observed. (Bug #32286186)

     * MySQL Shell&#039;s upgrade checker utility
       util.checkForServerUpgrade() now checks for spatial data
       columns that were originally created in MySQL 5.6. The
       underlying data type for such columns in MySQL 5.6 does
       not match their underlying data type in MySQL 8.0, so
       upgrade of the table is prohibited, and it must be
       recreated. (Bug #32257211, Bug #101944)

     * When MySQL Shell casts a string to a boolean value, the
       operation is now case insensitive. Previously, the
       results could differ between platforms. (Bug #32217910)

     * When MySQL Shell&#039;s \warnings command was used to show
       warnings after each statement, warnings were not
       displayed for a classic MySQL protocol connection. (Bug
       #32151137)

     * MySQL Shell&#039;s parallel table import utility
       util.importTable() now checks whether an uploaded object
       is a directory, and excludes these from wildcard matching
       that was specified for files. (Bug #31991122)

     * MySQL Shell&#039;s dump loading utility util.loadDump() can
       split oversized chunks of data into smaller chunks for
       upload. Previously, if loading was stopped then resumed
       partway through this stage, the rows in the smaller
       chunks that were already loaded were not taken into
       account and skipped, which could lead to deadlocks. The
       utility&#039;s progress file now records the smaller chunks
       individually so that they can be skipped if the load is
       stopped and resumed. (Bug #31961688)

     * An event that contained a sequence of two semi-colons
       caused MySQL Shell&#039;s instance dump utility
       util.dumpInstance(), schema dump utility
       util.dumpSchemas(), and table dump utility
       util.dumpTables() to enter an infinite loop looking for
       delimiters. (Bug #31820571)

     * The decodeColumns option for MySQL Shell&#039;s parallel table
       import utility util.importTable() could be specified
       without an accompanying columns option, resulting in the
       import stopping with an error. (Bug #31407058)

     * If a script that was run interactively in MySQL Shell&#039;s
       Python mode did not have a newline character at the end,
       and the script ended with a multiline command, MySQL
       Shell waited for input instead of processing the command.
       The user had to press Enter to finish running the script,
       and the last line of the script was incorrectly saved in
       MySQL Shell&#039;s code history. MySQL Shell now adds an empty
       line after processing a script input stream, to ensure
       that this situation does not occur. (Bug #30765725)

     * MySQL Shell used a different character set for collations
       depending on whether X Protocol or classic MySQL protocol
       was used to connect to the MySQL server instance, leading
       to inconsistency and in some situations, errors. For
       MySQL 5.7 instances, MySQL Shell now uses a SET NAMES
       statement to set all the relevant session system
       variables to the utf8mb4 character set. For MySQL 8.0
       instances, MySQL Shell now sets the collation_connection
       system variable to the utf8mb4_0900_ai_ci character set.
       (Bug #30516645)

Enjoy and thanks for the support!

On Behalf of the MySQL Engineering Team,
Nawaz Nazeer Ahamed
</pre>]]></description>
            <dc:creator>Nawaz Nazeer Ahamed</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 13:03:03 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696004,696004#msg-696004</guid>
            <title>MySQL Connector/NET 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696004,696004#msg-696004</link>
            <description><![CDATA[ Dear MySQL users,<br />
<br />
MySQL Connector/NET 8.0.24 is the latest General Availability release<br />
of the MySQL Connector/NET 8.0 series. This version supports .NET 5.0<br />
and the X DevAPI, which enables application developers to write code<br />
that combines the strengths of the relational and document models<br />
using a modern, NoSQL-like syntax that does not assume previous<br />
experience writing traditional SQL.<br />
<br />
To learn more about how to write applications using the X DevAPI, see<br />
<br />
  <a href="http://dev.mysql.com/doc/x-devapi-userguide/en/"  rel="nofollow">http://dev.mysql.com/doc/x-devapi-userguide/en/</a><br />
<br />
For more information about how the X DevAPI is implemented in<br />
Connector/NET, see<br />
<br />
  <a href="http://dev.mysql.com/doc/dev/connector-net"  rel="nofollow">http://dev.mysql.com/doc/dev/connector-net</a><br />
<br />
NuGet packages provide functionality at a project level. To get the<br />
full set of features available in Connector/NET such as availability<br />
in the GAC, integration with Visual Studio&#039;s Entity Framework Designer<br />
and integration with MySQL for Visual Studio, installation through the<br />
MySQL Installer or the stand-alone MSI is required.<br />
<br />
Please note that the X DevAPI requires at least MySQL Server version<br />
8.0 or higher with the X Plugin enabled. For general documentation<br />
about how to get started using MySQL as a document store, see<br />
<br />
  <a href="http://dev.mysql.com/doc/refman/8.0/en/document-store.html"  rel="nofollow">http://dev.mysql.com/doc/refman/8.0/en/document-store.html</a><br />
<br />
To download MySQL Connector/NET 8.0.24, see<br />
<br />
  <a href="http://dev.mysql.com/downloads/connector/net/"  rel="nofollow">http://dev.mysql.com/downloads/connector/net/</a><br />
<br />
Installation instructions can be found at<br />
<br />
  <a href="https://dev.mysql.com/doc/connector-net/en/connector-net-installation.html"  rel="nofollow">https://dev.mysql.com/doc/connector-net/en/connector-net-installation.html</a><br />
<br />
Changes in MySQL Connector/NET 8.0.24 (2021-04-20, General<br />
Availability)<br />
<br />
Functionality Added or Changed<br />
<br />
<br />
   * The IgnorePrepare connection-string option was deprecated<br />
     in the Connector/NET 8.0.23 release and removed in the<br />
     Connector/NET 8.0.24 release.<br />
     The removed option instructed Connector/NET to ignore all<br />
     calls to MySqlCommand.Prepare() that were made using the<br />
     classic MySQL protocol. (Bug #31872906)<br />
<br />
   * Improved server disconnection handling of X Protocol<br />
     connections now creates a log entry and returns an error<br />
     message, as needed, after Connector/NET receives a<br />
     connection-close notice from the server. Connector/NET<br />
     detects three new types of warning notices.<br />
<br />
     Connection idle notice.  This notice applies to a server<br />
     connection that remains idle for longer than the relevant<br />
     timeout setting. Connector/NET closes the connection when<br />
     it receives the notice in an active session or while a<br />
     new session is being created. An attempt to use the<br />
     invalid session returns the &quot;Connection closed. Reason:<br />
     connection idle too long&quot; error message.<br />
<br />
     Server shutdown notice.  If a connection-close notice is<br />
     received in a session as a result of a server shutdown,<br />
     Connector/NET terminates the session with the &quot;Connection<br />
     closed. Reason: server shutdown&quot; error message. All other<br />
     sessions that are connected to the same endpoint are<br />
     removed from the pool, if connection pooling is used.<br />
<br />
     Connection killed notice.  If the connection being killed<br />
     from another client session, Connector/NET closes the<br />
     connection when it receives the notice in an active<br />
     session or while a new session is being created. An<br />
     attempt to use the invalid session returns the<br />
     &quot;Connection closed. Reason: connection killed by a<br />
     different session&quot; error message.<br />
<br />
   * If a classic MySQL protocol connection experiences a<br />
     server timeout, Connector/NET now reports more precise<br />
     disconnection information to affected .NET applications<br />
     when the server provides improved error messages.<br />
<br />
   * Previously, Connector/NET added client support for the<br />
     MySQL Enterprise Edition SASL LDAP authentication plugin<br />
     with SCRAM-SHA-1 and SCRAM-SHA-256 as authentication<br />
     methods. Connector/NET now also supports GSSAPI/Kerberos<br />
     as an alternative authentication method for classic MySQL<br />
     protocol connections. SASL-based LDAP authentication does<br />
     not apply to clients running macOS.<br />
<br />
   * The SSH Tunneling (port forwarding) feature, which was<br />
     added to support MySQL products in making secure<br />
     connections on Windows, is no longer needed by other<br />
     products. Now, using an alternative such as OCI or<br />
     SSH.NET to create a tunnel is preferred. The related<br />
     connection options (SshHostName, SshKeyFile,<br />
     SshPassPhrase, SshPassword, SshPort, and SshUserName) are<br />
     no longer valid when making Connector/NET connections,<br />
     starting with this release.<br />
<br />
Bugs Fixed<br />
<br />
<br />
   * Pound symbols in JSON columns were interpreted improperly<br />
     when using accent-sensitive collation. (Bug #32429236)<br />
<br />
   * Several data types could not be mapped by running<br />
     Scaffold-DbContext on valid MySQL tables. This fix<br />
     upgrades Microsoft Entity Framework libraries to the<br />
     latest and also adds all previously excluded mappings to<br />
     the EFCore and EFCore5 projects. (Bug #32424742, Bug<br />
     #102381)<br />
<br />
   * Constructing a regular expression for each read<br />
     diminished the performance of Connector/NET. This fix<br />
     limits the construction to one instance, which now is<br />
     reused. (Bug #32386454, Bug #101714)<br />
<br />
   * A data table declared using valid database.table syntax<br />
     within an Entity Framework model could have extra<br />
     database names in the generated query (for example,<br />
     database.database.table). (Bug #32358174, Bug #101236)<br />
<br />
   * Incomplete GUID mapping in the Entity Framework Core<br />
     implementation caused an error when the Contains method<br />
     was used to filter records. (Bug #32173133, Bug #93398)<br />
<br />
   * Additional error codes now prevent unexpected exceptions<br />
     after a query. Thanks to Stanislav Revin for the patch.<br />
     (Bug #32150115, Bug #101592)<br />
<br />
   * An exception was thrown if any CHAR(36) columns<br />
     containing a NULL value were referenced in a query. New<br />
     validation now checks for NULL values when the<br />
     MySqlDbType member is Guid. (Bug #32049837, Bug #101252)<br />
<br />
<br />
On Behalf of Oracle/MySQL Engineering Team,<br />
Tvarita Jain]]></description>
            <dc:creator>Tvarita Jain</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 12:11:22 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696002,696002#msg-696002</guid>
            <title>MySQL Connector/Node.js 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696002,696002#msg-696002</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL users, 

MySQL Connector/Node.js is a new Node.js driver for use with the X 
DevAPI. This release, v8.0.24, is a maintenance release of the 
MySQL Connector/Node.js 8.0 series. 

The X DevAPI enables application developers to write code that combines 
the strengths of the relational and document models using a modern, 
NoSQL-like syntax that does not assume previous experience writing 
traditional SQL. 

MySQL Connector/Node.js can be downloaded through npm (see 
  <a href="https://www.npmjs.com/package/@mysql/xdevapi"  rel="nofollow">https://www.npmjs.com/package/@mysql/xdevapi</a> for details) or from 
  <a href="https://dev.mysql.com/downloads/connector/nodejs/"  rel="nofollow">https://dev.mysql.com/downloads/connector/nodejs/</a>. 

To learn more about how to write applications using the X DevAPI, see 
  <a href="http://dev.mysql.com/doc/x-devapi-userguide/en/"  rel="nofollow">http://dev.mysql.com/doc/x-devapi-userguide/en/</a>. 
For more information about how the X DevAPI is implemented in MySQL 
Connector/Node.js, and its usage, see 
  <a href="http://dev.mysql.com/doc/dev/connector-nodejs/"  rel="nofollow">http://dev.mysql.com/doc/dev/connector-nodejs/</a>. 

Please note that the X DevAPI requires at least MySQL Server version 
8.0 or higher with the X Plugin enabled. For general documentation 
about how to get started using MySQL as a document store, see 
  <a href="http://dev.mysql.com/doc/refman/8.0/en/document-store.html"  rel="nofollow">http://dev.mysql.com/doc/refman/8.0/en/document-store.html</a>. 

Changes in MySQL Connector/Node.js 8.0.24 (2021-04-20, General Availability)

     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed

     * Important Change: Starting in this version,
       Connector/Node.js will ignore compatibility with
       End-of-life Node.js versions. If you are planning to
       upgrade, make sure you are using Node.js 12.0.0 or
       higher.

     * Connector/Node.js no longer guarantees compatibility with
       End-of-life Node.js versions. Today this means only
       Node.js 12.0.0 or higher are officially supported.

     * Improved the inline documentation and added functionality
       for users to generate it locally using JSDoc. See
       CONTRIBUTING.md for instructions on how to generate the
       HTML documentation.

     * Improved server disconnection handling of X Protocol
       connections now creates a log entry and returns an error
       message, as needed, after Connector/Node.js receives a
       connection-close notice from the server.
       Connector/Node.js detects three new types of warning
       notices.

          + Connection idle notice: This notice applies to a
            server connection that remains idle for longer than
            the relevant timeout setting. Connector/Node.js
            closes the connection when it receives the notice in
            an active session or while a new session is being
            created. An attempt to use the invalid session
            returns the &quot;Connection closed. Reason: connection
            idle too long&quot; error message.

          + Server shutdown notice: If a connection-close notice
            is received in a session as a result of a server
            shutdown, Connector/Node.js terminates the session
            with the &quot;Connection closed. Reason: server
            shutdown&quot; error message. All other sessions that are
            connected to the same endpoint are removed from the
            pool, if connection pooling is used.

          + Connection killed notice: If the connection being
            killed from another client session,
            Connector/Node.js closes the connection when it
            receives the notice in an active session or while a
            new session is being created. An attempt to use the
            invalid session returns the &quot;Connection closed.
            Reason: connection killed by a different session&quot;
            error message.

Bugs Fixed

     * The getSession() method now executes release() if a
       getSession() exception is raised; as ot was not releasing
       the connection to the pool. (Bug #32366743, Bug #101928)

     * The Session.getDefaultSchema() method now returned
       &#039;undefined&#039; instead of a valid Schema instance if a
       default schema is not set. (Bug #32136490)

                 
On Behalf of the MySQL Engineering Team,
Sreedhar S

</pre>]]></description>
            <dc:creator>Sreedhar Sreedhargadda</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 11:54:59 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,696001,696001#msg-696001</guid>
            <title>MySQL Connector/C++ 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,696001,696001#msg-696001</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL users,

MySQL Connector/C++ 8.0.24 is a new release version of the MySQL
Connector/C++ 8.0 series.

Connector/C++ 8.0 can be used to access MySQL implementing Document
Store or in a traditional way, using SQL queries. It allows writing
both C++ and plain C applications using X DevAPI and X DevAPI for C.
It also supports the legacy API of Connector/C++ 1.1 based on JDBC4.

To learn more about how to write applications using X DevAPI, see
&quot;X DevAPI User Guide&quot; at

  <a href="https://dev.mysql.com/doc/x-devapi-userguide/en/"  rel="nofollow">https://dev.mysql.com/doc/x-devapi-userguide/en/</a>

See also &quot;X DevAPI Reference&quot; at

  <a href="https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html"  rel="nofollow">https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html</a>

and &quot;X DevAPI for C Reference&quot; at

  <a href="https://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html"  rel="nofollow">https://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html</a>

For generic information on using Connector/C++ 8.0, see

  <a href="https://dev.mysql.com/doc/dev/connector-cpp/"  rel="nofollow">https://dev.mysql.com/doc/dev/connector-cpp/</a>

For general documentation about how to get started using MySQL
as a document store, see

  <a href="http://dev.mysql.com/doc/refman/8.0/en/document-store.html"  rel="nofollow">http://dev.mysql.com/doc/refman/8.0/en/document-store.html</a>

To download MySQL Connector/C++ 8.0.24, see the &quot;General Availability (GA)
Releases&quot; tab at

  <a href="https://dev.mysql.com/downloads/connector/cpp/"  rel="nofollow">https://dev.mysql.com/downloads/connector/cpp/</a>

Changes in MySQL Connector/C++ 8.0.24 (2021-04-20, General
Availability)

Connection Management Notes


   * Previously, for client applications that use the legacy
     JDBC API (that is, not X DevAPI or X DevAPI for C), if
     the connection to the server was not used within the
     period specified by the wait_timeout system variable and
     the server closed the connection, the client received no
     notification of the reason. Typically, the client would
     see Lost connection to MySQL server during query
     (CR_SERVER_LOST) or MySQL server has gone away
     (CR_SERVER_GONE_ERROR).
     In such cases, the server now writes the reason to the
     connection before closing it, and client receives a more
     informative error message, The client was disconnected by
     the server because of inactivity. See wait_timeout and
     interactive_timeout for configuring this behavior.
     (ER_CLIENT_INTERACTION_TIMEOUT).
     The previous behavior still applies for client
     connections to older servers and connections to the
     server by older clients.

   * For connections made using X Plugin, if client with a
     connection to a server remains idle (not sending to the
     server) for longer than the relevant X Plugin timeout
     setting (read, write, or wait timeout), X Plugin closes
     the connection. If any of these timeouts occur, the
     plugin returns a warning notice with the error code
     ER_IO_READ_ERROR to the client application.
     For such connections, X Plugin now also sends a warning
     notice if a connection is actively closed due to a server
     shutdown, or by the connection being killed from another
     client session. In the case of a server shutdown, the
     warning notice is sent to all authenticated X Protocol
     clients with open connections, with the
     ER_SERVER_SHUTDOWN error code. In the case of a killed
     connection, the warning notice is sent to the relevant
     client with the ER_SESSION_WAS_KILLED error code, unless
     the connection was killed during SQL execution, in which
     case a fatal error is returned with the
     ER_QUERY_INTERRUPTED error code.
     If connection pooling is used and a connection close
     notice is received in a session as a result of a server
     shutdown, all other idle sessions that are connected to
     the same endpoint are removed from the pool.
     Client applications can use the warning notices to
     display to users, or to analyze the reason for
     disconnection and decide whether to attempt reconnection
     to the same server, or to a different server.

Packaging Notes


   * Connector/C++ packages now include sasl2 modules due to
     connection failures for accounts that use the
     authentication_ldap_sasl authentication plugin. (Bug
     #32175836)

Bugs Fixed


   * Upon connecting to the server, Connector/C++ executed a
     number of SHOW [SESSION] VARIABLES statements to retrieve
     system variable values. Such statements involve locking
     in the server, so they are now avoided in favor of SELECT
     @@var_name statements.
     Additionally, Connector/C++ was trying to fetch the value
     of the max_statement_time system variable, which has been
     renamed to max_execution_time. Connector/C++ now uses the
     correct variable name, with the result that
     getQueryTimeout() and setQueryTimeout() now work properly
     for both Statement and Prepared Statement objects. (Bug
     #28928712, Bug #93201)

   * DatabaseMetaData.getProcedures() failed when the
     metadataUseInfoSchema connection option was false. (Bug
     #24371558)

On Behalf of the Oracle/MySQL Engineering Team,
Tvarita Jain


</pre>]]></description>
            <dc:creator>Tvarita Jain</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 11:47:02 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,695997,695997#msg-695997</guid>
            <title>MySQL Connector/ODBC 8.0.24 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,695997,695997#msg-695997</link>
            <description><![CDATA[ <pre class="bbcode">
Dear MySQL users,

MySQL Connector/ODBC 8.0.24 is a new version in the MySQL Connector/ODBC
8.0 series, the ODBC driver for the MySQL Server.

The available downloads include both a Unicode driver and an ANSI driver
based on the same modern codebase. Please select the driver type you
need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with the latest MySQL server version 8.0.

This release of the MySQL ODBC driver is conforming to the ODBC 3.8
specification. It contains implementations of key 3.8 features,
including self-identification as a ODBC 3.8 driver, streaming of out (for
binary types only), and support of the SQL_ATTR_RESET_CONNECTION
connection attribute (for the Unicode driver only).

The release is now available in source and binary form for a number of
platforms from our download pages at

  <a href="https://dev.mysql.com/downloads/connector/odbc/"  rel="nofollow">https://dev.mysql.com/downloads/connector/odbc/</a>

For information on installing, please see the documentation at

  <a href="https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html"  rel="nofollow">https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html</a>

Enjoy and thanks for your support!


Changes in MySQL Connector/ODBC 8.0.24 (2021-04-20, General Availability)

Functionality Added or Changed


     * Previously, if the connection to the server was not used
       within the period specified by the wait_timeout system
       variable and the server closed the connection, the client
       received no notification of the reason. Typically, the
       client would see Lost connection to MySQL server during
       query (CR_SERVER_LOST) or MySQL server has gone away
       (CR_SERVER_GONE_ERROR).
       In such cases, the server now writes the reason to the
       connection before closing it, and the client receives a
       more informative error message: The client was
       disconnected by the server because of inactivity. See
       wait_timeout and interactive_timeout for configuring this
       behavior. (ER_CLIENT_INTERACTION_TIMEOUT).
       The previous behavior still applies for client
       connections to older servers and connections to the
       server by older clients.

     * If a classic MySQL protocol connection experiences a
       server timeout, Connector/ODBC now reports more precise
       disconnection information from the server.

Bugs Fixed


     * The ODBC SQLProcedureColumns function returns incomplete
       results, fetches after usage would only return the first
       40 parameters.
       The workaround was to increase the group_concat_max_len
       size, for example &#039;group-concat-max-len = 1000000&#039; under
       [mysqld]. (Bug #32504915, Bug #102589)

     * MySQL 8.0.24 added a new ER_CLIENT_INTERACTION_TIMEOUT
       error code, and it caused the ODBC driver to report the
       wrong SQLSTATE HY000 instead of 08S01 after the
       connection is terminated on the server by
       wait_/_interactive timeout. The ODBC driver is now linked
       against libmysqlclient 8.0.24 to handle this situation.
       (Bug #32394545)

On Behalf of Oracle/MySQL Engineering Team,
Gipson Pulla
</pre>]]></description>
            <dc:creator>Gipson Pulla</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 09:19:19 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?3,695996,695996#msg-695996</guid>
            <title>MySQL Router 8.0.24 for MySQL Server 8.0 and 5.7 has been released (no replies)</title>
            <link>https://forums.mysql.com/read.php?3,695996,695996#msg-695996</link>
            <description><![CDATA[ Dear MySQL users,<br />
<br />
MySQL Router 8.0.24 is a new release for MySQL Router 8.0 series.<br />
<br />
MySQL Router 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7.<br />
Please upgrade to MySQL Router 8.0.24.<br />
<br />
The MySQL Router is a new building block for high availability solutions<br />
based on MySQL InnoDB clusters.<br />
<br />
By taking advantage of the new Group Replication technology, and<br />
combined with the MySQL Shell, InnoDB clusters provide an integrated<br />
solution for high availability and scalability for InnoDB based MySQL<br />
databases, that does not require advanced MySQL expertise.<br />
<br />
The deployment of applications with high availability requirements is<br />
greatly simplified by MySQL Router. MySQL client connections are<br />
transparently routed to online members of a InnoDB cluster, with MySQL<br />
server outages and cluster reconfigurations being automatically handled<br />
by the Router.<br />
<br />
To download MySQL Router 8.0.24, see the &quot;General Availability (GA)<br />
Releases&quot; tab at <a href="http://dev.mysql.com/downloads/router"  rel="nofollow">http://dev.mysql.com/downloads/router</a>. Package<br />
binaries are available for several platforms and also as a source code<br />
download.<br />
<br />
Documentation for MySQL Router can be found at<br />
<a href="http://dev.mysql.com/doc/mysql-router/en/"  rel="nofollow">http://dev.mysql.com/doc/mysql-router/en/</a><br />
<br />
Enjoy!<br />
<br />
<pre class="bbcode">
Changes in MySQL Router 8.0.24 (2021-04-20)


     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


     * Changed the default ports used by Router, and default
       behavior depends on the --conf-base-port bootstrap
       option.
       If --conf-base-port is not set, then the associated
       bind_port values begin at 6446; Classic (RW 6446, RO
       6447) and X Protocol (RW 6448, RO 6449). Additionally,
       now setting --conf-base-port to 0 uses the old default
       ports of Classic (RW 6446, RO 6447) and X Protocol (RW
       64460, RO 64470).
       Reason: the previous default X Protocol ports (64460 and
       64470) are defined as &quot;Dynamic Ports&quot; as per RFC 6335.

     * Previously, Router bound the incoming socket at startup
       and kept it open even if no destinations were available.
       Now Router only binds to the socket if destinations are
       available, and otherwise closes the incoming sockets.
       This also means Load-Balancers know whether Router can
       handle traffic.

Bugs Fixed


     * The mysqlrouter.conf file in Debian Router packages did
       not set the run directory to an absolute path name,
       resulting in package installation errors. (Bug #32620788)

     * Disabled code-cache when compiling on Solaris to avoid
       &#039;invalid bytecode&#039; errors; previously it was only
       disabled for sun-cc builds. (Bug #32567899)

     * When using first-available policy and static routing, it
       was possible that the router wouldn&#039;t start and emit an
       error similar to &quot;plugin &#039;routing:test_default&#039; start
       failed: routing:test_default: Failed setting up TCP
       service&quot;; fixed race condition on start-up between &#039;is
       running&#039; and &#039;start socket acceptor&#039;. (Bug #32565479)

     * Fixed assertion that a previous destination list
       contained primary destinations after connecting to a
       primary node failed. This assertion was firing because
       the primary destinations were not properly recognized
       during refresh. (Bug #32543464)

     * Network transfers larger than the socket send buffer,
       such as large result sets or queries, could terminate the
       connection. (Bug #32543049)

     * Now return an std::errc::operation_would_block error code
       if write() blocks and no data is written; before 0 was
       returned. (Bug #32542170)

     * Configuring a second Router instance on the same machine
       without the --name parameter would yield unexpected
       errors related to file cleanup. (Bug #32517802)

     * Router would report as READY before the sockets were
       open; so now reports it after the socket acceptors are
       set up. (Bug #32429409)

     * Network loss before connect() was resulting in long
       failover times as it depended on the operating system&#039;s
       network timeouts. The connect_timeout option was not
       honored, but is now applied before connecting. (Bug
       #32428113)

     * Router no longer relies upon the MySQL instance&#039;s
       availability logic for wait-primary-failover. Instead, it
       now checks the metadata-cache&#039;s replicaset info for a new
       Primary. This is because GR membership does not change is
       the network between Router and the Primary is lost. (Bug
       #32393421)

     * After a network loss between Router and a group
       replication PRIMARY (but not network loss between group
       replication members), the wait for the failover by Router
       did not timeout after 10 seconds, and instead the
       connection remained locked. (Bug #32338771)

     * Configuration options expecting numeric values would
       allow hex and octal values; but now only completely
       numeric values are allowed. For example,
       --config-base-port=0xff now reports an error. (Bug
       #32297657)

     * Improved the DEBUG logging mechanism to include the
       following information: host:port, execution time, OK/ERR
       information, and row count. In addition, now log one
       message instead of separate before/after messages. (Bug
       #32293818)

     * The REST endpoint timeout check changed from waiting for
       &quot;timeout + request time&quot; to waiting until the timeout
       expires. (Bug #32252500)
</pre>]]></description>
            <dc:creator>Bjørn Munch</dc:creator>
            <category>Announcements</category>
            <pubDate>Tue, 20 Apr 2021 09:18:18 +0000</pubDate>
        </item>
    </channel>
</rss>
