Question 1

How do I switch between MySQL and PostgreSQL with BQB?

Accepted Answer

Use ToSql() for MySQL with ? placeholders and ToPgsql() for PostgreSQL with $n syntax; BQB handles parameter conversion automatically, so you only need to change the method call.

Question 2

BQB or GORM for a Go web app?

Accepted Answer

Choose BQB if you prefer writing raw SQL and need lightweight parameter handling; opt for GORM if you want a full ORM with model definitions, migrations, and relationship management.

Question 3

How to build a dynamic WHERE clause with optional filters in BQB?

Accepted Answer

Use Optional() combined with And() and Or() methods to add conditions based on logic, ensuring clauses are omitted when unused, as shown in the advanced examples with filterAdult and filterChild.

Question 4

Does BQB support transactions or connection pooling?

Accepted Answer

No, BQB is solely a query builder; transactions and connections must be managed separately using Go's database/sql package or libraries like sqlx.

Question 5

How to prevent SQL injection when using BQB's Embedder for dynamic table names?

Accepted Answer

The Embedder interface embeds raw values, so only use it for trusted, hard-coded strings like sort directions or schema names, and never for user input without strict validation.

Question 6

Can BQB handle complex subqueries and CTEs?

Accepted Answer

Yes, by nesting Query instances within others using the ? placeholder, but you must write the SQL syntax manually, as BQB doesn't abstract subquery constructs.

bqb

What is bqb?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions