Our great sponsors
| NORM | sqlc | |
|---|---|---|
| 3 | 169 | |
| 108 | 10,950 | |
| - | 6.5% | |
| 7.6 | 9.6 | |
| 5 months ago | 4 days ago | |
| PLpgSQL | Go | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
NORM
- Is ORM still an anti-pattern?
-
Looking at the Postgres NORM project
Repo: https://github.com/hettie-d/NORM
-
Contributing to the No Object Relational Mapping Project (NORM) for PostgreSQL
No, because we support the specific return type with strong Postgres types. If you look at the package here: https://github.com/hettie-d/NORM/blob/master/sql/account_pkg.sql
sqlc
-
Give Up Sooner
"Is there a way to get sqlc to use pointers for nullable columns instead of the sql.Null types?"
-
Show HN: Sqlbind a Python library to compose raw SQL
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).
- API completa em Golang - Parte 7
-
ORMs are nice but they are the wrong abstraction
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.
- API completa em Golang - Parte 6
-
Go ORMs Compared
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.
-
Type-safe Data Access in Go using Prisma and sqlc
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.
-
Level UP your RDBMS Productivity in GO
Now, we are going to generate the code. For this purpose, we are going to use sqlc.
-
What 3rd-party libraries do you use often/all the time?
https://github.com/sqlc-dev/sqlc — for use with //go:generate
- API completa em Golang - Parte 1
What are some alternatives?
Norm.net - Norm.net is an innovative and high-performance Database Access for .NET Standard 2.1 and higher
sqlx - general purpose extensions to golang's database/sql
SQLpage - SQL-only webapp builder, empowering data analysts to build websites and applications quickly
GORM - The fantastic ORM library for Golang, aims to be developer friendly
postgres_air
SQLBoiler - Generate a Go ORM tailored to your database schema.
potygen - Postgres SQL Parser and type generator
ent - An entity framework for Go
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
jet - Type safe SQL builder with code generation and automatic query result data mapping
sqlite-fast - A high performance, low allocation SQLite wrapper targeting .NET Standard 2.0.
pgx - PostgreSQL driver and toolkit for Go