sqlbunny.io

What It Is

SQLBunny is a code-generation-based Go ORM. Its core idea is not to rely heavily on reflection or generic interfaces at runtime, but to generate Go structs and database access methods from model definitions. The source material emphasizes that the generated code is statically typed and uses “No interface{},” which is clearly appealing to Go developers who care about type safety, compile-time checks, and IDE autocomplete.

Core Capabilities

In terms of functionality, SQLBunny covers the main parts of an ORM workflow: model definitions, standard types, querying, query binding, query logging, relationships, transactions, migrations, hooks, and plugin development. In the example, a book model is defined via Model and Field; after running sqlbunny, it generates a models.Book struct, which can call Insert(ctx) to insert records and models.Books().All(ctx) to query them. It also supports automatic migration generation by comparing the current migrations with defined models; relationship helper functions; enums; reusable Structs that can be expanded into multiple columns; and custom Go types in fields.

Language, Databases, and Ecosystem

SQLBunny is clearly aimed at Go. For database support, the source text states that PostgreSQL is fully supported, while MySQL and other databases are still “coming soon.” So if your team mainly uses Postgres, its compatibility story is relatively clear; if you depend on MySQL, multiple databases, or cloud database compatibility layers, you should evaluate it carefully. In terms of ecosystem, it originated as a fork of SQLBoiler and provides documentation entry points for the BunnyID plugin, Hooks plugin, and writing plugins, suggesting that it has some extensibility design.

Pricing and Documentation

The crawled content does not disclose its pricing model, paid plans, license, or open-source status, so commercial cost and compliance risk cannot be assessed. On the documentation side, the page links to a standalone documentation site and lists sections such as Getting Started, Types, Models, Querying, Transactions, and Migrations. The structure appears fairly complete; however, the current source text only includes a table of contents and a brief example, so it is not possible to confirm documentation depth, update frequency, or coverage of production issues.

Pros, Cons, and Who It’s For

Its strengths are type safety, clear generated code, explicit PostgreSQL support, and built-in migration and relationship helpers. Its weaknesses are limited database coverage and missing information about whether it is open or closed source, the maintenance team, community size, and pricing. It is suitable for backend teams using Go + PostgreSQL that want to reduce handwritten SQL data-access code without sacrificing type safety. There is no basis in the source text to judge accessibility from China, so it should be marked as unknown. Alternatives include SQLBoiler, GORM, Ent, Bun, and sqlc.