The latest from the MySQL community

As part of building the MySQL Community, we are going to publish a curated overview of MySQL and database news and events that you might have missed over the last period.

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)

Opening Up the MySQL Bug Process
TL;DR - Oracle makes more progress on opening the development process for MySQL to include open bug tracking.

…

On May 26, The MySQL Community Team at Oracle welcomed MySQL contributors, customers, partners, and community members to the MySQL Contributor Summit at the Oracle Redwood Shores campus, with additional participants joining remotely.  The Contributor Summit brought Oracle engineers and community contributors together to exchange ideas, share ongoing work, and explore opportunities to collaborate on […]

The MySQL team has been working hard to foster innovation, strengthen collaboration with our community, support meaningful contributions, and grow the broader MySQL ecosystem through greater openness and transparency. We believe MySQL is at its best when everyone can see how progress is being made, where work is happening, and how issues move through the […]

I am excited to be speaking at COSCUP 2026 in Taipei, Taiwan on August 8th and 9th. COSCUP (Conference for Open Source Coders, Users and Promoters) is one of the largest open source conferences in Asia, and it is always a privilege to present to the engaged and technically sharp community there.

I am excited to be speaking at COSCUP 2026 in Taipei, Taiwan on August 8th and 9th. COSCUP (Conference for Open Source Coders, Users and Promoters) is one of the largest open source conferences in Asia, and it is always a privilege to present to the engaged and technically sharp community there.

MySQL 9.7 LTS is here, establishing the new MySQL 9.7.x Long-Term Support release line. For organizations running MySQL today, this is the right time to evaluate upgrade plans and move toward a current, supported foundation. It is also a good moment for teams standardizing their database strategy to take a fresh look at MySQL. Whether […]

Modern applications often pass JSON back and forth with the database server. With MySQL, we have had great JSON support, but working with relational data as JSON usually meant generating documents manually with built-in JSON functions. When an application sent JSON back to the server, we often had to break that document apart and write […]

You have a table. You need to serve it over HTTP.

The standard path requires you to write a service in Node or Python or Go, wire up routes, translate query parameters into WHERE clauses, serialize rows as JSON, add auth middleware, deploy it separately from the database, and then watch two dashboards instead of one.

None of that is particularly hard. It's just infrastructure that re-derives what your schema already says. For internal tools, admin panels, mobile app backends, and prototypes, that's often most of the work between the schema and a usable API.

vsql-rest skips that layer. It's inspired by PostgREST, with a similar idea: your tables as REST endpoints, no code required. The MySQL world also has Oracle's MySQL REST Service, which takes a …

As part of building the MySQL Community, we are going to publish a curated overview of MySQL and database news and events that you might have missed over the last period.

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 only)

Summary of MySQL Public Discussion #4: Updates and Improvements to Contributions
TL;DR - Summary from Oracle on contribution paths and review of MySQL Contributor Summit

…

A few months ago, I was asking myself how to insert in two tables in a single round-trip to the database.  I wanted to do that to optimize a process.  My optimization involved splitting a table in two, which would need inserting in two tables atomically.  The downside was changing an auto-commit INSERT to a transaction with two inserts, which was changing the shape of the workload