Community journal

The latest from the MySQL community

Ideas, releases, practical guides, and perspectives from the people building with MySQL.

Follow the feed
Showing entries 1 to 10 of 45610 « Previous | Next »
Announcing VillageSQL Server 0.0.8

VillageSQL Server 0.0.8 is now available. This release is about using extensions from applications: through prepared statements, with text in other character sets, and with the server protected when an extension function throws an exception.

Highlights of this release include the following:

  • Functions that take custom types work in prepared statements.
  • Extensions built with the 0.0.8 SDK can tell raw bytes from text.
  • When a function in an extension built with the 0.0.8 SDK throws an exception, only that statement fails, and the server keeps running.

Custom types in prepared statements

Many applications keep values out of the SQL text. They send the query once as a prepared statement and pass the values separately, and most MySQL connectors can work this way. In 0.0.8, functions that take custom …

[Read more]
Modernize on Your Terms: How Nutanix and AWS Accelerate Migrations, Simplify Operations, and Enable AI

Learn how Nutanix and AWS help organizations migrate workloads without refactoring, simplify hybrid cloud operations, and build a flexible foundation for AI.

Why MySQL OR is slower than IN

Queries with OR conditions are commonly used to implement business logic.

However, it might be slower than we expected. 

Although the query below scans only 1 million rows, it runs for 6,7254 seconds.

# User@Host: msandbox[msandbox] @ localhost [127.0.0.1]  Id:   188
# Schema:   Last_errno: 1160  Killed: 0
# Query_time: 67254.081455  Lock_time: 0.000006  Rows_sent: 1  Rows_examined: 1000000  Rows_affected: 0  Bytes_sent: 0
...
SELECT COUNT(*) FROM db1.sbtest1 WHERE id = 1 OR id = 2 OR id = 3 OR id = 4 OR id = 5 OR id = 6 OR id = 7 OR id = 8 OR id = 9 ...
...

The CPU profile indicates that 99% of CPU time was spent in Item_cond_or::val_int() on MySQL 8.4.

connection
└ mysql_execute_command → Sql_cmd_dml::execute → Query_expression::ExecuteIteratorQuery
  └ AggregateIterator::Read                                99.80%
    └ FilterIterator::Read                                 99.80% …
[Read more]
Building PlanetScale with Insights Agent

We've always used PlanetScale to build PlanetScale. So when we built Insights Agent, our own databases were the first place we ran it to see what kind of gains we could get. Insights Agent identifies problematic queries or schema using Query Insights, finds the code responsible for them, and opens a pull request with a fix. Our Rails API is a large, busy app, which makes it a good testing ground.

We know a thing or two about databases over here, so our databases are already quite well optimized. Even so, Insights Agent has been able to find a bunch of wins for us, continuing our drive towards the most efficient database possible.

Here are three (of many) examples of how we tested and used Insights Agent in the weeks leading up to launch, and how we used these experiences to make the product better.

…

[Read more]
Amazon RDS for MySQL LTS version 9.7 is now generally available

Today, Amazon Relational Database Service (Amazon RDS) announced support for MySQL version 9.7, the latest Long-Term Support (LTS) major version from the MySQL community, in addition to MySQL 8.0 and 8.4. As with prior versions, you can bring your existing MySQL code, applications and tools to Amazon RDS. For customers who need more time to upgrade, Amazon RDS continues to offer earlier major versions under RDS Extended Support: MySQL 8.0 entered RDS Extended Support on August 1, 2026, and MySQL 5.7 remains available under RDS Extended Support through June 30, 2029.

MySQL 9.7 is the second LTS Release from the community, following MySQL 8.4. It includes the features delivered across the 9.0 through 9.6 Innovation Releases and adds 9.7-specific capabilities. In this post, we …

[Read more]
Village News: MySQL News + Events (18 November 2026)

Welcome back to Village News, our curated roundup of MySQL and database news. This week, MariaDB shipped its Q4 maintenance releases across four LTS series, and OurSQL Foundation opened a call for MySQL-compatible projects to share its FOSDEM 2027 booth.

If you want to get these updates, just subscribe to the blog.

Enjoy!

MySQL News

Note: Aggregated MySQL news can be found at Planet for MySQL Community and Planet MySQL (Oracle curated)

David Stokes: "Nine Times Out of Ten, It's MySQL"
Maria Nesterova, OurSQL Foundation Blog

TL;DR …

[Read more]
David Stokes: “Nine Times Out of Ten, It’s MySQL”

David Stokes has been part of MySQL’s story under every one of its owners. He joined MySQL AB as a PHP developer, ran its certification program, and stayed through the Sun and Oracle acquisitions, spending about a decade on Oracle’s MySQL Community team alongside Frédéric Descamps. After Oracle and a spell at Percona, he now works at DBeaver, a database tool that connects to more than 170 databases, which gives him an unusually wide view of where MySQL stands. We talked about what each owner did to MySQL, why he walked away from Oracle, why Postgres is “free as in puppy”, and what the MySQL world must do to win the next generation of developers.

MySQL Shorts - Episode 107 - MySQL Transactions: Maintain Data Consistency

MySQL transactions help maintain data consistency by grouping related SQL updates so they can be committed together or rolled back when an operation fails. See how START TRANSACTION and ROLLBACK work with inventory updates and database constraints to reverse uncommitted changes, and explore the MySQL transaction documentation: https://dev.mysql.com/doc/refman/26.10/en/commit.html

MySQL Community Public Meeting #6: Building Momentum Together

On October 22, 2026, we held our sixth public meeting with the MySQL community. The theme, “Continued Development Momentum,” captured the progress well: more capabilities in Community Edition, community contributions reaching users, and clearer paths for getting involved. Our priorities remain delivering innovation into Community Edition, growing the ecosystem, and making MySQL development more transparent […]

How VillageSQL does documentation

We've heard positive feedback about VillageSQL's documentation, so we wanted to share a bit more on how we build it and how we hope to evolve it. VillageSQL Server tracks upstream MySQL and adds an extension framework, so the documentation has two moving targets. We pull in upstream changes with each MySQL release, and VillageSQL's own changes land daily in the dev branch and ship with each release. We believe that it's important for a complex project to provide accurate documentation that is updated as frequently as code ships. This is easier said than done. We use AI extensively to generate our docs, but we believe it's critical to have a human as a review gate before any change is shipped. AI makes mistakes, so we make it prove every change to itself and to humans by testing against a running server.

Frequent readers of the VillageSQL docs will also notice a recent redesign. The …

[Read more]
« Previous | Next »