sqlx VS Squirrel

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.

But using a query builder, something like squirrel or (plug) bqb, allows you to actually write SQL (or something close to it) when you need it but also handles the nasty string building bits. Though I agree that ORMs are not always bad, especially for small projects with well-defined scope.

But if I want to replace Gorm, I will using https://github.com/Masterminds/squirrel

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

Plug for bqb as a query builder, but there's also squirrel which works pretty well too.

Query Builder. Similar to Squirrel, but more flexible and performant.

I personally do the no ORM approach, often combining query-builders with SQL drivers (sqlx + squirrel) as to avoid raw SQL in my code. You can build composable query this way and it lessens the likelihood of someone accidentally creating a SQL injection vulnerability.

SQL Builders (think squirrel or goqu)

golang https://github.com/Masterminds/squirrel

Constructing sql by concat strings has a few issues, its repetitive and hard to assemble certain queries conditionally, and at least in golang its easy to write code vulnerable to sql injection and you can avoid that by using types

Libraries like Jooq and SQLDelight include what I'm talking about and then build on top of it with codegen which is even nicer since it adds compiler safety

But even without codegen you'd still a much nicer interface than manually hacking together strings as the Golang example others have linked shows: https://github.com/Masterminds/squirrel

Also checkout https://github.com/Masterminds/squirrel