pq VS pgxtutorial

Following the completion of the series — Secure and performant full-stack authentication system using rust (actix-web) and sveltekit and Secure and performant full-stack authentication system using Python (Django) and SvelteKit — I felt I should keep the streak by building an equivalent system in PURE go with very minimal external dependencies. We won't use any fancy web framework apart from httprouter and other basic dependencies including a database driver (pq), and redis client. As usual, we'll be using SvelteKit at the front end, favouring JSDoc instead of TypeScript. The combination is ecstatic!

Go’s standard library was not built to include any specific database drivers. So we need to install a third party package. In this case we are going to install https://github.com/lib/pq. Run following command:

For Postgres the driver comes from "github.com/lib/pq" and then it is just "postgres".

With regards to 2. -- also, it looks like there's an important unfixed issue https://github.com/lib/pq/issues/939. I haven't verified whether the issue is up to date.

Postgres (pure Go): https://github.com/lib/pq [*]Postgres (uses cgo): https://github.com/jbarham/gopgsqldriver Postgres (pure Go): https://github.com/jackc/pgx [*]

lib/pq 7.3k Stars, Used by 63k

I am using the lib/pq driver. is there a driver that does allow for this syntax or is there something I can change?

# Clone my repository with any of the following commands: $ gh repo clone henvic/pgxtutorial $ git clone https://github.com/henvic/pgxtutorial.git $ git clone [email protected]:henvic/pgxtutorial.git # then: $ cd pgxtutorial # Create a database $ psql -c "CREATE DATABASE pgxtutorial;" # Set the environment variable PGDATABASE $ export PGDATABASE=pgxtutorial # Run migrations $ tern migrate -m ./migrations # Run all tests passing INTEGRATION_TESTDB explicitly $ INTEGRATION_TESTDB=true go test -v ./... # Execute application $ go run ./cmd/pgxtutorial 2021/11/22 07:21:21 HTTP server listening at localhost:8080 2021/11/22 07:21:21 gRPC server listening at 127.0.0.1:8082

oh, I also have defined database.PGX (https://github.com/henvic/pgxtutorial/blob/main/internal/dat...), which is a little more scarier. I'll get back about that too, but this one is perhaps even more useless, and there might be a better way to solve the issue I want to try to avoid with it.