Show HN: VillageSQL = MySQL and Extensions

VillageSQL just dropped as a MySQL-compatible “build-your-own-upgrades” server, and the internet immediately split into two camps: the tinkerers and the terrified. It’s an alpha, open-source fork that adds an extension system—think plug-ins for your database—so you can create custom data types and functions while staying MySQL-friendly. It’s not ready for real-world use yet, and yes, you have to compile it yourself. Developers called that out as the classic “boss fight” before the fun begins, while the team points to the docs and promises Docker later.

But the real sparks flew around two hot buttons. First, the eternal “what should be your database ID” spat reignited when one user warned that using random-looking IDs (called UUIDs) can slow things down, linking a PSA on performance (source). Cue eye rolls and “here we go again” memes. Second—and spicier—someone found VillageSQL’s AI add-on and called it “terrifying” (vsql-ai). The idea of AI agents poking around your data freaked some people out, while others argued it’s the future and this is exactly what databases should be learning to do.

So today’s vibe: bold new plug-in database playground vs. goosebumps over AI in your data. And as always, a side of classic database culture wars.