HN Reader

We built VillageSQL because we love MySQL, but we’ve watched the ecosystem stagnate while PostgreSQL flourished with extensions like pgvector and pg_textsearch. We wanted to give MySQL that same extensibility so teams don’t have to migrate databases just to keep building nowadays. VillageSQL is an open-source, tracking fork of MySQL that is a drop-in replacement and adds a true extension framework.

How it works: +It’s a drop-in replacement

+We added an interface to load external shared libraries (.so files) as extensions.

+You define custom data types and functions (with indexes coming soon) that run natively inside the engine.

+We are launching with a few proof-of-concept extensions: vsql-ai, vsql-uuid, vsql-crypto, vsql-network-address. We’re currently in alpha.

We know forking MySQL is a big swing, but we believe the community needs a way to innovate on the core engine without waiting for Oracle and in a way that is easier to use than plug-ins.

The code is open source here: https://github.com/villagesql/villagesql-server

We’d love your feedback. Happy to answer any questions about the implementation!