pgx VS Squirrel

Sometimes, backend developers tend to opt for an ORM library because it provides an abstraction between your app and the database and thus there is little or no need to write raw queries and migrations which is nice. However, if you want to get better at writing queries (SQL for example), you need to learn how to build your repositories without an ORM. To open a database handle, you can either do it directly from the database driver or do it from database/sql with the driver passed into it. I will be opening the connection with database/sql together with pgx which is a driver and toolkit for PostgreSQL. Walk with me.

The infrastructure layer contains the concrete implementation of the repository domain interface ActivityRepository in the struct DbActivityRepository. This repository implementation uses the Postgres driver pgx and plain SQL to store the activity in the database. It uses the database transaction from the context, since the transaction was initiated by the application service.

For building the RESTful Point of Sale service API, I've considered and selected a combination of technologies that would work seamlessly together. For handling HTTP requests and responses, using the Gin HTTP web framework would make sense because I think it seems complete and popular among Go community too. To ensure data integrity and persistence, I'm using PostgreSQL database with pgx as the database driver, the reason I choose PostgreSQL because it is the most popular relational database to use in production and offers efficient Go integration. I'm also implementing caching using Redis with go-redis client library, which provides powerful in-memory data storage capabilities.

If you are willing to commit to working only with Postgres, I highly recommend pgx. Be sure you get the latest version github.com/jackc/pgx/v5. This gives you the full power of interacting with Postgres without going through an intermediate lowest-common-denominator library.

It uses pg package and pgx driver under the hood.

Starting off, is there any reason you're calling out to the CLI, instead of just using a Postgres driver like pgx? Shelling out to the command line should always be a last resort where possible as a software engineer.

For maintaining state I use PostgreSQL. Driver: https://github.com/jackc/pgx (I use the pgxpools) Along with Sqlc for generating database models and allowing me to focus on just building queries in DBeaver. https://sqlc.dev/

An example of what I'm looking for can be found here https://github.com/jackc/pgx/wiki/Getting-started-with-pgx-through-database-sql/c9f798b4d9a500fcf93931df2464af969d68f516

Except pgx recommends using their native interface, not database/sql, for performance and extra features [0], so it's not that simple in practice.

[0]: https://github.com/jackc/pgx#choosing-between-the-pgx-and-da...

pgx is “PostgreSQL driver and toolkit for Go”. Take a look at https://github.com/jackc/pgx

It uses Gin as the HTTP framework and PostgreSQL as the database with pgx as the driver and Squirrel as the query builder. It also utilizes Redis as the caching layer with go-redis as the client.

I would add Squirrel to PGX https://github.com/Masterminds/squirrel

I have written about this before, and my thoughts always settle on using a query builder. I've built a simple one, which works for what I need, but there are more feature complete ones out there such as squirrel. I've also written about how you can implement a simple CRUD library for database interactions using generics and query building to have that nice middle-ground between an ORM and query building.

Now for the dynamic queries you have to be really careful to prevent SQL injections, there are bunch of different ways to do it but I typically recommend using a package such as squirrel that lets you do this easily, you use it to generate the plain SQL you need (and then use sqlx, database/sql, pgx or whatever you prefer) or use it directly querying the database directly.

Here are 2 options for you * https://github.com/huandu/go-sqlbuilder * https://github.com/Masterminds/squirrel

https://www.reddit.com/r/golang/comments/vq98ud/what_sql_library_are_you_using/ Jet havn't used but is one that looks promising! Otherwise I'm one of the purests, db/sql and https://github.com/Masterminds/squirrel

I think he means an sql builder like squirrel. This allows dynamic queries, but more important you can reuse function that build a where clause so you can get a count and query with that.

I'd rather suggest the use of tools more aligned with the core concepts of the language such as sqlx, which is an extension of the database/sql standard library. It allows you to use models/structs to map your tables but you have more control over the SQL statements you use to perform queries and the like. You can combine sqlx with Squirrel to build queries from composable parts.

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.

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