exposure-notifications-server VS sqlc

Not a small one, but a real-life one, the exposure-notifications-server is usually what I like to recommend, keep in mind that you probably need a bit of Go knowledge and context before looking at it so perhaps it isn't the best introductory project to look at; however I recommend you to bookmark it for future reference.

Google's Exposure Notification Reference Serve is a real life example of what you're asking for.

It's also popular to hate on golang-standards/project-layout here (mostly due to its misleading name), but then you'll find Google's own project following its general approach.

Context logger (https://github.com/moonr-app/crypto-signal-trading-bot/tree/main/internal/shared/logging) inspired by the one Google wrote for the Covid 19 server (https://github.com/google/exposure-notifications-server)

Other redditors mentioned some good resources, I'm going to shamelessly plug mine as well; either way after you are done with whatever tutorial you use I recommend you to look at the Exposure Notifications Server, reading the source code should help you learn other best practices.

No worries, I was just saying isolate any database related operations specific to a package. https://github.com/google/exposure-notifications-server this is a pretty great example of a real world sql /go.

You may want to checkout the "Exposure Notifications Server" project; I also have a similar (educational) project that uses the Repository Pattern.

However, IMO, the closest to an "official" layout would be the "Exposure Notifications Server" project, but even then I think it really depends on the business domain of your project which in the end affects naming and the final project structure.

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