On April 21st, 2026, we released MySQL 9.7.0, the latest Long-Term Support release.

As always, we are grateful to the MySQL community for helping improve MySQL with bug reports, patches, pull requests, and continued feedback. Community contributions help make MySQL better for everyone, and we are happy to recognize the contributors whose work was included in this release.

In MySQL 9.7.0, we received contributions across several areas, including Connector/NET, the MySQL Server Optimizer, Parser, Prepared Statements, Performance Schema, Data Types, and Charsets.

Connector / NET

  • #119338 – Added LINQ query support for StartsWith and EndsWith. Arguments sent using these methods are now correctly translated – Ma Liming

Optimizer

  • #112737 – Conditions on const tables and previously joined tables were not consistently taken into account when building ranges – Xingyu Yang
  • #116611 – User-defined histogram import could fail for BIGINT data – Tianfeng Li
  • #118512 – The missing semi join condition could cause incorrect results – Jingqi Tian (Alibaba)
  • #119922 – Fixed excessive generation of histogram background update errors – Tony Chen (Amazon)
  • #119995 – Under certain circumstances, find_in_set() could return incorrect results – Jingqi Tian

Parser

  • #116084 – In an EXPLAIN expanded query, join order hints were not printed with valid syntax – Kaiwang Chen

Prepared Statements

  • #119236 – Prepared statements with mismatched parameter types could enter infinite loops and consume 100% CPU after re-preparation – Alex Xing

Performance Schema

  • #115844 – Fixed an erroneous comment in storage/perfschema/table_host.h – Sho Nakazono

Data Types

  • #118658 – Fixed an issue with NULL detection for temporal data types in derived tables after a derived merge – Xingyu Yang (Tencent)

Charsets

  • #114830 – MySQL converted collation information for date and time data types in .ibd metadata while the data dictionary reported NULL character set and collation values – Venkatesh Prasad Venugopal (Percona)

MySQL depends on the community to help improve, evolve, and strengthen the project. Some of the best improvements come from people like you: developers, DBAs, users, and community members who take the time to share fixes, ideas, and feedback. The MySQL Community Team will be publishing quarterly metrics and working with the community to increase participation and contributions in a variety of areas. Have a patch, fix, or improvement you would like to share? The MySQL Community Developer Guide is a great place to start, with details on how to contribute code, request features, and participate in the community. You can also join the conversation in the MySQL Community GitHub Discussions, where contributors can ask questions, share feedback, and collaborate with the developer community. When you are ready, send us a pull request through one of the MySQL GitHub repositories or submit your patch through Bugs MySQL. You will need to sign the Oracle Contributor Agreement before we can accept the contribution, but once that is in place, we are excited to see what you build.

Thank you to everyone who contributed to MySQL 9.7.0. Every patch, bug report, review, and piece of feedback helps move MySQL forward. Your contributions make MySQL stronger, more reliable, easier to use, and better for the millions of developers, DBAs, and organizations who depend on it every day.