Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

VillageSQL = MySQL and Extensions

Details

External ID
46900796
Source
HN
Company
—
Product
VillageSQL = MySQL and Extensions
Website domain
github.com
Launched
Feb. 5, 2026
Cohort
—
Upvotes
27
Upvotes percentile
0.7331536388140162
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

INSTALL EXTENSION vsql-complex; CREATE TABLE t (val COMPLEX);Look, MySQL is awesome [flamewar incoming?]. But the ecosystem has stagnated. Why?No permissionless innovation. Postgres has flourished because people can change the core of the database (look at pgvector and pg_textsearch), without having to get their changes accepted upstream.(This, btw, is what powered GitHub's early success: you can fork a repo and make changes without needing the owners' approval)VillageSQL is a tracking fork of MySQL (open source, ofc) that adds an extension framework: * Drop-in replacement* Add custom data types and functions (with indexes coming soon)* we wrote example extensions (vsql-ai, -uuid, crypto, etc.)* you have a better idea for an extension* my CEO submitted a Show HN post but linked to the announcement blog; help me show him hackers want code first* I'm particularly proud of the friendly C++ API to add custom functions (in func_builder.h)That link again is https://github.com/villagesql/villagesql-server(Oh, and I get to work with the former TL of Google's BigTable and Colossus, so we care about doing databases Right)

Enrichment

Theme
database infrastructure and developer tools
Vertical
Horizontal
Function
Data infrastructure
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
mysql fork with additional features
Manually corrected
False

Could you build this?

No Creating a modular dynamic extension architecture and engine fork for MySQL requires deep systems programming expertise in the MySQL/C++ core.

What it would actually take: A developer must fork MySQL's C++ codebase, rewrite or hook into the query parser, planner, storage engine interface, and type subsystem to support dynamic shared-library loading (similar to PostgreSQL's PG_MODULE_MAGIC and extension API). The hardest technical challenges are creating stable ABI/API hooks into MySQL's tightly coupled internal data structures, managing memory safely across plugin boundaries, and maintaining full transactional safety and replication compatibility with upstream MySQL updates.

Discussion

6 comments analyzed.

Competitors mentioned: MariaDB

Concerns raised: Risk of generating millions of rows from incorrect queries, Risk of sending millions of LLM API requests unintentionally, MySQL ecosystem fragmentation

Feature requests: Query safety limits or guardrails, Cost controls for LLM API usage

Competitors

Other products that read as similar to this one — 151 launches clear the similarity bar, closest 8 shown.

Attention rank: #55 of 152 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 98 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a data infrastructure tool for Media & entertainment yet.