squid
trilogy
Our great sponsors
| squid | trilogy | |
|---|---|---|
| 2 | 1 | |
| 130 | 256 | |
| - | - | |
| 0.0 | 0.0 | |
| about 1 year ago | almost 2 years ago | |
| TypeScript | TypeScript | |
| 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
trilogy
-
Trilogy – GitHub-built MySQL client library written in C
Naming is hard and conflicts are easy, but this project clashes with my own project called Trilogy. Both for SQL-family, although mine is in the JavaScript realm. I'm not too surprised someone followed the logic did to get the name.
Not a huge project but has some users, and I still try to work on it to get the typings (TypeScript) where I want them.
https://github.com/citycide/trilogy
What are some alternatives?
ship-hold - data access framework for Postgresql on nodejs
hotstuff - theleo.zone/thermal-model source code (formerly thermalmodel.com)
stackql-middleware - Middleware solution to allow clients to query back end APIs using SQL
trilogy - Trilogy is a client library for MySQL-compatible database servers, designed for performance, flexibility, and ease of embedding.
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
DotNet-ORM-Cookbook - This repository is meant to show how to perform common tasks using C# with variety of ORMs.
aurora - CLI tool that orchestrates prisma files in a way that allows multiple .prisma files with cross-relations
Tortuga Chain - A fluent ORM for .NET
node-starter-kit - Node.js / GraphQL project template pre-configured with TypeScript, PostgreSQL, login flow, transactional emails, unit tests, CI/CD workflow.
Sequel - Sequel: The Database Toolkit for Ruby
knex-types - Generate TypeScript definitions (types) from a PostgreSQL database schema.