gnorm
sqlparser-rs
gnorm | sqlparser-rs | |
---|---|---|
3 | 12 | |
482 | 2,443 | |
0.0% | 2.4% | |
0.0 | 9.3 | |
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
sqlparser-rs
-
Introducing SQLPage : write websites entirely in SQL
sqlparser to parse SQL queries and detect variable bindings
-
Understanding the SQL AST and what can be done with it
So to start with this, I looked into SQL parsing and found this library https://github.com/sqlparser-rs/sqlparser-rs
-
Supabase Logs: open source logging server
We switched to an open source alternative, the rust-based sqlparser-rs library, contributing a few updates for the BigQuery dialect.
- Parsing SQL with Rust
-
Writing a SQL LS in Rust - Looking for Coding Companions.
I have experience with sqlparser-rs (for my sqlpage project), but it does not track the source code location of the parsed data structures (yet).
-
Pure Python Distributed SQL Engine
It uses https://github.com/sqlparser-rs/sqlparser-rs as the parser and lexer. The binder, planner, optimizer and executor are in Python. The optimizer stage only works on the logical plan and the rules are heuristic only.
-
Parsing / Recursive Descent Parser
That code could be copied directly from some real-world examples - sqlparser-rs code looks pretty much exactly the same.
https://github.com/sqlparser-rs/sqlparser-rs
-
RisingLight is an OLAP database system for educational purpose
Also neat to find the SQL parser library they use.
- We Went All in on Sqlc/Pgx for Postgres and Go
- “Swift is the only language I could find with over 100 keywords”
What are some alternatives?
pggen - A database first code generator focused on postgres
sled - the champagne of beta embedded databases
proteus - A simple tool for generating an application's data access layer.
goyesql - Parse SQL files with multiple named queries and automatically prepare and scan them into structs.
jet - Type safe SQL builder with code generation and automatic query result data mapping
sqlite
pike - Generate CRUD gRPC backends from single YAML description.
kube - Rust Kubernetes client and controller runtime
ccgo
prettytable-rs - A rust library to print aligned and formatted tables
pggen - Generate type-safe Go for any Postgres query. If Postgres can run the query, pggen can generate code for it.
go - The Go programming language