sqlx VS sqlc

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

This is the same situation I saw 20 years ago. Back then, all the managers were pushing development in Oracle tools. Those managers grew up on Oracle and Java was too modern for them. Now the situation is similar. Managers used to do things in Java and now they are still pushing Java. In fact, today Java brings nothing but problems. When I see a new project starting on Java it is always some big desperation. For a comparison of Java and Go, just look at the documentation for SQL. For go: https://pkg.go.dev/database/sql (31 pages) and maybe https://jmoiron.github.io/sqlx/ (12 pages). In Java only one class is 59 pages (https://docs.oracle.com/javase/8/docs/api/java/sql/ResultSet.html) and look how many of those documents there are: https://docs.oracle.com/en/java/javase/13/docs/api/java.sql/java/sql/package-summary.html and on top of that we have javax.sql - https://docs.oracle.com/javase/8/docs/api/javax/sql/package-summary.html And even then you use Hibernate for example, where the documentation has 11 manuals and of those the User Guide has 353 pages - https://docs.jboss.org/hibernate/orm/6.2/userguide/html\_single/Hibernate\_User\_Guide.html

sqlx

If you care about performance you might want to avoid an ORM all together and just write out the queries you need. We use sqlx in those cases.

or in general for accessing databases? * sqlx: general purpose extensions to database/sql * sqlc: generate type safe code from queries * squirrel: fluent SQL generator

https://github.com/jmoiron/sqlx and github.com/lib/pq are pretty solid, this is what i go to.

The amount of packages imported is kind of a thing I want to remove. There is, for example, MySQL package but I use PG. Also, for many things I need sqlx, sometimes database/sql + carta. I would love to standardize all my database handling to make it simple, concise, and efficient;

Implement the Repository interface by writing the queries in code, perhaps using some solution like Squirrel or sqlx.

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

It's also the domain used for releases and other artifacts (after a redirect from github.com). There's going to be a lot of broken builds today:

    $ curl -i -L https://github.com/kyleconroy/sqlc/releases/download/v1.17.0/sqlc_1.17.0_linux_amd64.tar.gz

Why don't you use sqlc + pgx? What's missing from the two?

https://github.com/kyleconroy/sqlc

https://github.com/jackc/pgx

I’ve seen people put automatically generated code (e.g. from https://sqlc.dev/ or https://entgo.io/) inside a sub-internal package (e.g. db/internal) with the intention of never exposing it to the rest of the code. The rest of the code works with structs and functions exported by the parent package, which internally delegated to the generated code.

I have been using: https://sqlc.dev/ With pgx for Postgres and liking it so far. It does code generation. But seems pretty easy to maintain. And there is no reflection at runtime, so performance is good.

I used sqlc[1] for golang, while it’s very cool and keeps things simple, at the end I switched to gorm as I needed hooks and dynamic queries where annoying to write. I could have build these things myself on top, but that would have been a homegrown orm in the end. But as every orm, gorm also has its problems, pick you poison.

[1] https://sqlc.dev/

Gorm is a orn not a api framework. Api frameworks consist of gin, echo, and a few others I can’t name off my head. If you’re looking for a orm(something to simplify the queries you’re building. I would suggest bun or sqlc both are very light weight and fast.

Honestly, most people should just use generators like sqlc