squid
SQLDelight
Our great sponsors
squid | SQLDelight | |
---|---|---|
2 | 32 | |
130 | 5,917 | |
- | 1.8% | |
0.0 | 9.6 | |
about 1 year ago | 6 days ago | |
TypeScript | Kotlin | |
MIT License | 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.
squid
-
Don't use your ORM entities for everything – embrace the SQL
I guess I failed to set the context correctly given that you presented solutions for Clojure and Python, where it isn't as much of a problem since from the start the language fails to provide compiler guarantees you usually come to expect out of a SQL driver wrapper in typed languages (even though Clojure macros are probably powerful enough to allow this).
As a comparison, DX-wise this is no safer and is indeed very similar to the usual idiom in Go for example, where you just concatenate (pre-interpolated) SQL strings. But when you actually want the compiler to prove the correctness of your queries even in a rudimentary way, these .sql file solutions usually (if not, everytime) fail to provide the necessary external checker that processes templates and uses an accurate model of your database and SQL to verify that all used combinations make sense.
The closest thing to a proper take on this I've seen is https://github.com/andywer/squid with https://github.com/andywer/postguard which, although the SQL is inlined in the code, it uses the right approach for verifying correctness as far as I could tell in the little time I experimented with it.
-
"ORMs have a special place in my heart, not entirely unlike Brutus and Caesar: a dear friend who betrays you and leaves you to die a slow, painful death." – Taming SQL and ORMs with sqlc
For typescript and javascript, there's also squid + its companion project, postguard: https://github.com/andywer/squid
SQLDelight
-
querky – autogenerate Python functions and types for your SQL queries
This seems to be similar to https://github.com/cashapp/sqldelight, and I've always wanted a python equivalent!
In typescript, there are query builders (not talking about ORMs) that can basically do this within the type system, but that would be infeasible in python's type system. This approach (type/code generation is a good alternative, though I like using sqlalchemy / alembic to manage schemas/migrations.
One thing I'm curious about is how it knows the types of columns? I looked quickly at the Readme but didn't see it (probably a parameter somewhere I missed).
- I'm creating a REST API using KTOR. What's the best ORM to go with KTOR ?
-
KMM alternatives to Android Datastore & Room DB?
That functionality has existed for almost exactly a year
-
What were your negative experiences when adopting KMM?
- SQLDelight - great experience overall, the only issue that I found, was when that I made a database migration that worked on Android, but not on iOS (https://github.com/cashapp/sqldelight/issues/3812)
-
Adopting Kotlin Multiplatform Mobile(KMM) on 9GAGÂ App
Database - SQLDelight
-
Android Starter Template (hilt, ktor, coroutines, flow, modules, gradle.kts, version catalog, compose, MVVM, tests, GitHub CI)
room is a great example but like I said our data is kotlin-only so we tend to use libraries like sqlDelight.
-
Announcing new crate - "hugsqlx": turning SQLx queries into Rust functions
This seems similar to https://cashapp.github.io/sqldelight/ for kotlin, I think this approach is pretty neat, good luck with it!
-
ADVICE WANTED - Typescript PostgreSQL without ORM
Sounds like you want what SQLDelite offers, but for TypeScript. SQLDelite is only for Kotlin and SQLite though.
-
Why We're Moving on from Firebase
SQLDelight had neat built in support for this
https://cashapp.github.io/sqldelight/
-
Flyweight: An ORM for SQLite
You would really like sqldelight[1] then. It takes the concept of an ORM and flips it on its head. Instead of mapping function calls to SQL statements, it lets you write SQL statements and then generates classes for you that have methods for those statements.
For instance, you could have a SQL statement like getCardsForFight: select * from fights where cardId = ? and titleFight = ?, and it would generate a class that has a method getCardsForFight(cardId: number, titleFight: number).
[1]: https://github.com/cashapp/sqldelight