Gnorm Alternatives

Similar projects and alternatives to gnorm

go

2,068 119,564 10.0 Go gnorm VS go

The Go programming language
supabase

767 65,869 10.0 TypeScript gnorm VS supabase

The open source Firebase alternative.
SurveyJS

surveyjs.io sponsored

Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
sqlc

169 10,837 9.7 Go gnorm VS sqlc

Generate type-safe code from SQL
sqlx

144 11,742 9.2 Rust gnorm VS sqlx

🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite. (by launchbadge)
sqlite

72 - - gnorm VS sqlite
SQLBoiler

42 6,424 7.8 Go gnorm VS SQLBoiler

Generate a Go ORM tailored to your database schema.
goqu

23 2,232 5.6 Go gnorm VS goqu

SQL builder and query library for golang
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
sqlparser-rs

12 2,434 9.3 Rust gnorm VS sqlparser-rs

Extensible SQL Lexer and Parser for Rust
xo

16 3,563 6.4 Go gnorm VS xo

Command line tool to generate idiomatic Go code for SQL databases supporting PostgreSQL, MySQL, SQLite, Oracle, and Microsoft SQL Server (by xo)
pggen

11 268 6.6 Go gnorm VS pggen

Generate type-safe Go for any Postgres query. If Postgres can run the query, pggen can generate code for it.
pggen

2 58 0.6 Go gnorm VS pggen

A database first code generator focused on postgres (by opendoor)
ccgo

5 - - gnorm VS ccgo
proteus

2 195 3.5 Go gnorm VS proteus

A simple tool for generating an application's data access layer. (by jonbodner)
pike

2 307 0.0 Go gnorm VS pike

Generate CRUD gRPC backends from single YAML description. (by sashabaranov)
jet

26 2,025 8.1 Go gnorm VS jet

Type safe SQL builder with code generation and automatic query result data mapping
upper.io/db

6 3,479 5.1 Go gnorm VS upper.io/db

Data access layer for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.
rules_nixpkgs

5 264 9.0 Starlark gnorm VS rules_nixpkgs

Rules for importing Nixpkgs packages into Bazel.
pronto

4 6 0.0 Java gnorm VS pronto

Protobuf ORM (by CaperAi)
fileconst

1 2 0.0 Go gnorm VS fileconst

Discontinued Turns text file contents into Go constants
goyesql

2 44 0.0 Go gnorm VS goyesql

Parse SQL files with multiple named queries and automatically prepare and scan them into structs.
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better gnorm alternative or higher similarity.

Suggest an alternative to gnorm

gnorm reviews and mentions

Posts with mentions or reviews of gnorm. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-12.

Architecture Pitfalls: Don’t use your ORM entities for everything — embrace the SQL!
5 projects | /r/programming | 12 Jan 2023

Furthermore, there can be a lot of boilerplate queries we do that it's nice to not have to write, say, the same kind of delete query over and over. In the past I've used gnorm as one way of generating all that boilerplate code based on the actual database design, and it works reasonably well, but again it plays a similar role to an ORM.
Is it just me who doesn't agree with db first ORM model?
2 projects | /r/golang | 9 Apr 2022

I've used gnorm for that in the past for some code generation, and I had absolute control. Gnorm took care of the database inspection side of things, and I created the templates it used to generate the code. I had full control over generated models and code.
We Went All in on Sqlc/Pgx for Postgres and Go
31 projects | news.ycombinator.com | 8 Sep 2021

I'm a big fan of the database first code generator approach to talking to an SQL database, so much so that I wrote pggen[1] (not to be confused with pggen[2], as far as I can tell a sqlc fork, which I just recently learned about).
I'm a really big partisan of this approach, but I think I'd like to play the devil's advocate here and lay out some of the weaknesses of both a database first approach in general and sqlc in particular.
All database first approaches struggle with SQL metaprogramming when compared with a query builder library or an ORM. For the most part, this isn't an issue. Just writing SQL and using parameters correctly can get you very far, but there are a few times when you really need it. In particular, faceted search and pagination are both most naturally expressed via runtime metaprogramming of the SQL queries that you want to execute.
Another drawback is poor support from the database for this kind of approach. I only really know how postgres does here, and I'm not sure how well other databases expose their queries. When writing one of these tools you have to resort to tricks like creating temporary views in order infer the argument and return types of a query. This is mostly opaque to the user, but results in weird stuff bubbling up to the API like the tool not being able to infer nullability of arguments and return values well and not being able to support stuff like RETURNING in statements. sqlc is pretty brilliant because it works around this by reimplementing the whole parser and type checker for postgres in go, which is awesome, but also a lot of work to maintain and potentially subtlety wrong.
A minor drawback is that you have to retrain your users to write `x = ANY($1)` instead of `x IN ?`. Most ORMs and query builders seem to lean on their metaprogramming abilities to auto-convert array arguments in the host language into tuples. This is terrible and makes it really annoying when you want to actually pass an array into a query with an ORM/query builder, but it's the convention that everyone is used to.
There are some other issues that most of these tools seem to get wrong, but are not impossible in principle to deal with for a database first code generator. The biggest one is correct handling of migrations. Most of these tools, sqlc included, spit out the straight line "obvious" go code that most people would write to scan some data out of a db. They make a struct, then pass each of the field into Scan by reference to get filled in. This works great until you have a query like `SELECT * FROM foos WHERE field = $1` and then run `ALTER TABLE foos ADD COLUMN new_field text`. Now the deployed server is broken and you need to redeploy really fast as soon as you've run migrations. opendoor/pggen handles this, but I'm not aware of other database first code generators that do (though I could definitely have missed one).
Also the article is missing a few more tools in this space. https://github.com/xo/xo. https://github.com/gnormal/gnorm.
[1]: https://github.com/opendoor/pggen
A note from our sponsor - WorkOS
workos.com | 26 Apr 2024

The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →