Is go-sqlbuilder safe from SQL injection?

Yes, when using the Build() method with prepared statements, it properly escapes arguments. However, the interpolation feature has security warnings and should be avoided for sensitive data or with untrusted inputs.

How to use go-sqlbuilder with PostgreSQL?

Use the PostgreSQL flavor by calling PostgreSQL.NewSelectBuilder() or similar methods. This ensures correct syntax like $1 placeholders and supports PostgreSQL-specific features such as UPDATE ... FROM clauses.

go-sqlbuilder vs GORM: which one should I use?

Choose go-sqlbuilder for flexibility, control over SQL, and multi-database support without driver lock-in. GORM is better for rapid development with automatic migrations and relationships, but it's more opinionated and less customizable.

Can go-sqlbuilder generate database migrations?

No, it does not include migration tools. It's focused on SQL construction, so you'll need separate libraries like golang-migrate or manual scripts for schema changes.

How to handle nested queries with go-sqlbuilder?

Use builders as arguments in other builders, as shown in the nested SQL example where a SelectBuilder is passed to create subqueries, enabling complex logic like filtered JOINs or CTEs.

Best practices for using Struct as an ORM?

Define structs with db tags for column mapping, use field mappers like SnakeCaseMapper for naming conventions, and call Struct methods to generate SQL. Always scan results with Struct.Addr() for proper data binding to struct fields.

go-sqlbuilder — Flexible SQL Builder & ORM for Go

What is go-sqlbuilder?

go-sqlbuilder is a Go library for programmatically building SQL strings and acting as a zero-configuration ORM. It provides a flexible suite of builders for constructing SQL statements (SELECT, INSERT, UPDATE, etc.) that are compatible with Go's standard database/sql interfaces. It solves the problem of writing raw SQL strings manually, offering type-safe construction, argument escaping, and support for multiple database flavors.

Target Audience

Go developers who need to generate SQL queries dynamically, work with multiple database systems, or want a lightweight ORM alternative without the overhead of full-featured ORMs. It's particularly useful in enterprise environments with complex SQL requirements or custom database drivers.

Value Proposition

Developers choose go-sqlbuilder for its driver-agnostic design, performance optimization, and flexibility. It avoids locking users into a specific database driver or ORM framework, supports complex SQL scenarios like nested queries and reusable WHERE clauses, and includes a zero-config ORM that works with any database/sql-compatible driver.

A flexible and powerful SQL string builder library plus a zero-config ORM.

Use Cases

Best For

Dynamically building SQL queries with complex conditions and joins
Supporting multiple database systems (MySQL, PostgreSQL, SQLite, etc.) in one codebase
Creating reusable SQL templates for common query patterns
Implementing a lightweight ORM without external dependencies
Generating SQL for non-standard database systems or custom drivers
Writing type-safe SQL in Go without concatenating raw strings

Not Ideal For

Projects requiring full-featured ORM capabilities like automatic schema migrations, relationship management, and lazy loading
Teams that prefer integrated database solutions with built-in connection pooling and driver-specific optimizations
Applications with simple, static SQL queries where raw strings or lighter libraries like squirrel would suffice
Developers needing extensive community plugins or GUI tools for query building and debugging

Pros & Cons

Pros

Flexible SQL Building

Supports a comprehensive suite of builders for SELECT, INSERT, UPDATE, DELETE, CREATE TABLE, UNION, and CTEs, with nested queries and JOINs, as shown in the README examples for complex SQL scenarios.

Zero-Config ORM

The Struct type acts as a lightweight ORM, generating SQL from Go structs without database connection setup, allowing use with any database/sql-compatible driver for type-safe data mapping.

Reusable WHERE Clauses

WhereClause struct enables sharing and reusing conditions across different builders, improving code maintainability in enterprise environments with complex filtering logic.

Cloneable Builders

Builders can be cloned to create reusable templates, avoiding repeated setup and supporting safe concurrent use, as demonstrated in the global template example.

Cons

No Automatic Relationships

Lacks built-in support for model relationships like joins or lazy loading; developers must manually write JOINs and manage associations, unlike full ORMs such as GORM.

Interpolation Security Risks

The SQL interpolation feature for non-standard drivers comes with a security warning in the README, as it's less secure than using prepared statements and can be vulnerable to injection if misused.

Limited High-Level Abstractions

Focuses solely on SQL string construction, so tasks like schema migrations, transaction management, or connection pooling require additional libraries or custom code.

What is go-sqlbuilder?

Target Audience

Value Proposition

Use Cases

Best For

Dynamically building SQL queries with complex conditions and joins
Supporting multiple database systems (MySQL, PostgreSQL, SQLite, etc.) in one codebase
Creating reusable SQL templates for common query patterns
Implementing a lightweight ORM without external dependencies
Generating SQL for non-standard database systems or custom drivers
Writing type-safe SQL in Go without concatenating raw strings

Not Ideal For

Projects requiring full-featured ORM capabilities like automatic schema migrations, relationship management, and lazy loading
Teams that prefer integrated database solutions with built-in connection pooling and driver-specific optimizations
Applications with simple, static SQL queries where raw strings or lighter libraries like squirrel would suffice
Developers needing extensive community plugins or GUI tools for query building and debugging

Pros & Cons

Pros

Flexible SQL Building

Supports a comprehensive suite of builders for SELECT, INSERT, UPDATE, DELETE, CREATE TABLE, UNION, and CTEs, with nested queries and JOINs, as shown in the README examples for complex SQL scenarios.

Zero-Config ORM

The Struct type acts as a lightweight ORM, generating SQL from Go structs without database connection setup, allowing use with any database/sql-compatible driver for type-safe data mapping.

Reusable WHERE Clauses

WhereClause struct enables sharing and reusing conditions across different builders, improving code maintainability in enterprise environments with complex filtering logic.

Cloneable Builders

Builders can be cloned to create reusable templates, avoiding repeated setup and supporting safe concurrent use, as demonstrated in the global template example.

Cons

No Automatic Relationships

Lacks built-in support for model relationships like joins or lazy loading; developers must manually write JOINs and manage associations, unlike full ORMs such as GORM.

Interpolation Security Risks

The SQL interpolation feature for non-standard drivers comes with a security warning in the README, as it's less secure than using prepared statements and can be vulnerable to injection if misused.

Limited High-Level Abstractions

Focuses solely on SQL string construction, so tasks like schema migrations, transaction management, or connection pooling require additional libraries or custom code.

go-sqlbuilder

What is go-sqlbuilder?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

go-sqlbuilder

What is go-sqlbuilder?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?