goqu VS sqlc

For SQL, I'd probably go with goqu http://doug-martin.github.io/goqu/

I use goqu (https://github.com/doug-martin/goqu)

SQL Builders (think squirrel or goqu)

I've been looking for a package that allows me to build Postgres DDL statements in Golang. I'm currently using Goqu (https://github.com/doug-martin/goqu) for building statements and it works great, however it does not have support for building schemas. Basic things like creating tables, creating indexes. A great one in JavaScript can be found here: (https://knexjs.org/guide/schema-builder.html#essentials) I have been unable to find anything in Go, does anyone know of any packages like this?

Then use something like https://github.com/doug-martin/goqu to build the SQL.

Try this

We've been using goqu and it's super nice! although there are a ton of other query builders that could better fit your use-case.

If the statement is too dynamic to use query parameters I'd ideally use a dynamic query builder rather than concatenating strings. Goqu is a lib like that but I haven't yet used it personally https://github.com/doug-martin/goqu

"Is there a way to get sqlc to use pointers for nullable columns instead of the sql.Null types?"

I came across this yesterday for golang: https://sqlc.dev which is somewhat like what you want, maybe.

Not sure it allows you to parameterize table names but the basic idea is codegen from sql queries so you are working with go code (autocompletion etc).

Agreed, but tools like https://sqlc.dev, which I mention in the article, are a good trade-off that allows you to have verified, testable, SQL in your code.

sqlc is not strictly a conventional ORM. It offers a unique approach by generating Go code from SQL queries. This allows developers to write SQL, which sqlc then converts into type-safe Go code, reducing the boilerplate significantly. It ensures that your queries are syntactically correct and type-safe. sqlc is ideal for those who prefer writing SQL and are looking for an efficient way to integrate it into a Go application.

I was browsing awesome-go for ideas on how to setup my data access layer when I stumbled on sqlc. It seemed like a great option. Code generation is a strategy often used in the Go ecosystem and making my queries safe at compile time was an idea I really liked. Knex was great, but it required of me that I test thoroughly my queries at runtime and that I sanitize my query results to ensure type safety within my application.

Now, we are going to generate the code. For this purpose, we are going to use sqlc.

https://github.com/sqlc-dev/sqlc — for use with //go:generate