Extension
When something goes wrong inside MySQL, the server says so in the error log. It's what administrators already watch. Every entry carries a severity and an error code, and you can query it from performance_schema.error_log like any other table. It is the server's
VillageSQL
VillageSQL Server 0.0.5 is now available (and marked as the stable release for installs). This release is focused on the extension lifecycle: upgrading an extension in place, pinning the exact version you install, and seeing what's running. The extension framework also adds variable-length custom types
VillageSQL
MySQL's string matching is precise by design. LIKE '%shirt%' finds "shirt." It won't find "shrt" or "shrit" or anything a user actually typed when they meant "shirt." Handling that in MySQL means regex patterns that grow
VillageSQL
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
MySQL
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
VillageSQL
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
VillageSQL
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
We're on the road next week with three Bay Area events across the MySQL community. If you're at any of them, come say hi — in-person chats are so much more fun than messaging over GitHub. Oracle MySQL Community Contributors Summit - May 26, 2026 We'
MySQL still runs a remarkable share of the internet — 42% of the web is WordPress alone, plus many transactional applications you can probably name. But, the developer community is having a real argument about MySQL's future. * Stack Overflow's most recent survey put PostgreSQL ahead of MySQL
MySQL stores numbers well. What it can't do is treat a row's values as a multi-dimensional point in space. Standard MySQL spatial types are strictly limited to 2D (or 2D+Z) GIS data. It can’t check whether that point falls inside a bounding region,
MySQL
Most AI integrations with a database follow the same pattern: your application fetches rows, ships them to an AI API, waits for a response, then writes the result back. It works, but it means adding a service layer to do something that's conceptually simple—apply a function to
Every second, your database rows change: a new customer, a successful payment, a fresh sign-up. But while your business happens out in the world, your SQL logic is usually confined to the database itself. The world your application actually serves lives outside it—in webhooks, APIs, third-party services,