gnorm
sqlx
gnorm | sqlx | |
---|---|---|
3 | 145 | |
482 | 11,892 | |
0.0% | 3.0% | |
0.0 | 9.2 | |
almost 2 years ago | 6 days ago | |
JavaScript | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
gnorm
-
Architecture Pitfalls: Don’t use your ORM entities for everything — embrace the SQL!
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?
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
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
sqlx
-
A tale of TimescaleDB, SQLx and testing in Rust
For PostgreSQL, the most relevent part of the code is here. With this in mind I changed some things around to rely on schemas instead of databases and even simplified some parts of the implementation as this was always meant to be for internal use only..
-
Rust as a general application language
What exactly are you missing? I haven't really written "boring corporate backend stuff" in a few years but something like sqlx provides everything I've ever needed there.
-
Hey Rustaceans! Got a question? Ask here (49/2023)!
Badges are the little rectangles you typically see at the top of a crate's README: https://github.com/launchbadge/sqlx/blob/main/README.md
-
A new F# compiler feature: graph-based type-checking
SQLX has entered the chat [1].
[1] https://github.com/launchbadge/sqlx
-
Grimoire - A recipe management application.
Database : SqLite (using sqlx).
-
SQLX MSSQL Connection String Problem
The current (well, removed) MSSQL sqlx driver also doesn't support encrypted connections (https://github.com/launchbadge/sqlx/issues/1552), so it might work locally on an unnamed instance but not over the network until they add in the newer driver (which will be closed source but for an OSS project you should be able to request a free license I think)
-
Introducing SQLPage : write websites entirely in SQL
I'm considering making my own wrapper over lower-level database drivers. There are a lot of features in sqlx that I don't need, and the latest version seems to have removed useful data structures that SQLPage is using. It also removed support for SQL Server.
- SQLx 0.7 released! Offline mode usability improvements, performance fixes and major upgrades across the board!
- Is ORM still an anti-pattern?
-
MariaDB / SQLx - "Unknown Authentication Plugin"
add Ed25519 to AuthPlugin enum on https://github.com/launchbadge/sqlx/blob/061fdcabd72896d9bc3abb4ea4af6712a04bc0a8/sqlx-core/src/mysql/connection/auth.rs and implement them using these crates:
What are some alternatives?
pggen - A database first code generator focused on postgres
diesel - A safe, extensible ORM and Query Builder for Rust
sqlparser-rs - Extensible SQL Lexer and Parser for Rust
sea-orm - 🐚 An async & dynamic ORM for Rust
proteus - A simple tool for generating an application's data access layer.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
jet - Type safe SQL builder with code generation and automatic query result data mapping
rust-postgres - Native PostgreSQL driver for the Rust programming language
pike - Generate CRUD gRPC backends from single YAML description.
rbatis - Rust Compile Time ORM robustness,async, pure Rust Dynamic SQL
ccgo
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.