The latest from the MySQL community

When we introduced MySQL Studio, the goal was to bring the common parts of database development and analysis into one OCI workspace: SQL authoring, schema exploration, results visualization, and Ask Studio. The next step is making that workspace more useful during the everyday flow of MySQL work. For many MySQL developers, DBAs, and application teams, […]

VillageSQL launched with C++ as the language for writing extensions — C++ is familiar territory for MySQL developers. Rust has become a go-to language for systems and infrastructure developers: the same people who build database connectors, storage engines, and performance-critical services. VillageSQL's new Rust SDK adds it as a first-class option: write and ship a VillageSQL extension entirely in Rust without touching C++.

The architectural approach is similar to pgrx for PostgreSQL: bind directly to the server’s extension ABI rather than going through a client library. That's what opened PostgreSQL extension development to Rust developers, so it's the model we are following too.

What it looks like

We'll use a rot13 function to walk through the mechanics …

The MySQL Community team will be active across conferences, user group meetups, open source events, and regional community activities during the summer months. Whether you would like to hear about the latest MySQL 9.7 updates, meet the MySQL team, join a user group meetup, or connect with the broader open source and developer community, here […]

Modern applications generate and consume enormous amounts of semi-structured data. User profiles, product catalogs, IoT telemetry, application events, AI prompts, and content metadata rarely fit neatly into rigid relational schemas anymore. At the same time, enterprises still need the reliability, security, analytics, and operational maturity of a traditional database platform. This is where MySQL HeatWave […]

VillageSQL is a tracking fork of MySQL that adds the VillageSQL Extension Framework (VEF). Extensions are written in C++ (with a Rust SDK coming soon), packaged as .veb bundles, and installed with SQL. The fastest way to understand what VEF can do is to build something with it. To make getting started a bit easier, we published a skill you can run in a local CLI agent session (for example, Claude Code) to build new or port an existing extension.

Agents are “smart” so they could probably figure out how to build an extension on their own through trial and error. This skill allows you to save tokens by skipping some of that trial and error and using a framework/workflow that consistently works and has been improved through multiple iterations.

If you don't have VillageSQL installed already, you can get it with this install script:

curl -fsSL …

VillageSQL Server 0.0.4 is now available (and marked as the stable release for installs). 0.0.4 takes the parameterized types and SQL integration from 0.0.3 and extends them in two directions:

• smarter server reasoning (inference rules, custom aggregates)
• operational completeness (config, metrics, secrets management)

Extensions stop being things you install and hope work; they become things you can configure, monitor, and manage like any other part of the server.

Every MySQL ADO.NET provider looks reliable during development. The real differences appear later, when async performance breaks under load, licensing becomes a problem, or integrations with EF Core and cloud environments start creating friction. Read the full article to find the right MySQL .NET provider for your stack.

The post Top 4 MySQL ADO.NET Providers for 2026  appeared first on Devart Blog.

tidesdb-mysql is an experimental build that was developed to verify how TidesDB, the LSM-tree key/value engine, can work with MySQL 9.7 as a storage engine. The current build is v0.2.4, and it’s an experiment, not a finished product. So you can use it in your tests if you also want to try TidesDB with MySQL and compare with MariaDB

Why we made it

There was already a way to use TidesDB from SQL. It’s TideSQL, which loads the engine into MariaDB as ha_tidesdb, and it works fine. But it doesn’t work with MySQL. So we wanted TidesDB to work with MySQL 9.7.

MariaDB and MySQL share a lot of history, but they are not the same. We couldn’t just recompile the MariaDB plugin against MySQL headers and call it done. The one thing that stayed put through all of it was TidesDB itself, doing exactly what it does anywhere else. Only the server wrapped around was changed. In result we got our implementation, so if you’re …

As MySQL HeatWave environments continue to grow, many organizations prioritize scaling compute and storage resources while overlooking a critical area: database housekeeping. Inadequate maintenance practices can result in excessive storage consumption, longer backup and recovery times, replication lag, degraded query performance, and increased operational costs. This blog highlights key database hygiene and optimization strategies for […]

Overview

Servers Tested:

• MySQL 9.7.0 (PGO-enabled build released by Oracle)
• MySQL 9.7.0 Non-PGO (built without Profile-Guided Optimization — see BUILD.md)

Tier Configurations:

• Tier 2G: 2GB InnoDB buffer pool
• Tier 12G: 12GB InnoDB buffer pool
• Tier 32G: 32GB InnoDB buffer pool

View Results

Interactive Reports

The benchmark reports are available as interactive HTML pages at:

https://percona-lab-results.github.io/2026-pgo/index.html

Performance …