squid
ship-hold
Our great sponsors
| squid | ship-hold | |
|---|---|---|
| 2 | 1 | |
| 130 | 113 | |
| - | 0.9% | |
| 0.0 | 0.0 | |
| about 1 year ago | almost 2 years ago | |
| TypeScript | JavaScript | |
| MIT 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.
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
ship-hold
-
Which ORM/Query builder do you prefer using?
Ship-Hold https://github.com/zorro-del-caribe/ship-hold
What are some alternatives?
trilogy - TypeScript SQLite layer with support for both native C++ & pure JavaScript drivers.
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
stackql-middleware - Middleware solution to allow clients to query back end APIs using SQL
sqliterally - Lightweight SQL query builder
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
PostGUI - A React web application to query and share any PostgreSQL database.
DotNet-ORM-Cookbook - This repository is meant to show how to perform common tasks using C# with variety of ORMs.
PostgreSQL - PostgreSQL client for node.js.
Tortuga Chain - A fluent ORM for .NET
postgres - Postgres.js - The Fastest full featured PostgreSQL client for Node.js, Deno, Bun and CloudFlare
Sequel - Sequel: The Database Toolkit for Ruby
thin-backend - 🔥 Thin Backend is a Blazing Fast, Universal Web App Backend for Making Realtime Single Page Apps