sql-compose
tsql
| sql-compose | tsql | |
|---|---|---|
| 2 | 3 | |
| 2 | 11 | |
| - | - | |
| 4.1 | 6.8 | |
| over 3 years ago | 8 months ago | |
| Clojure | TypeScript | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
sql-compose
- Show HN: A tiny SQL query composer that scales infinitely
-
DenoDB
ORMs are unnecessary abstraction.
Check out https://github.com/ludbek/sql-compose
Tools like this are the future. It's so simple yet flexible enough to handle any complex queries.
It scales infinitely.
tsql
-
Kysely: TypeScript SQL Query Builder
We use in prod variant of no 1. [0]. Why? Because:
* it's extremely lightweight (built on pure, functional combinators)
* it allows us to use more complex patterns ie. convention where every json field ends with Json which is automatically parsed; which, unlike datatype alone, allows us to create composable query to fetch arbitrarily nested graphs and promoting single [$] key ie. to return list of emails as `string[]` not `{ email: string }[]` with `select email as [$] from Users` etc.
* has convenience combinators for things like constructing where clauses from monodb like queries
* all usual queries like CRUD, exists etc. and some more complex ie. insertIgnore, merge1n etc has convenient api
We resort to runtime type assertions [1] which works well for this and all other i/o; runtime type assertions are necessary for cases when your running service is incorrectly attached to old or future remote schema (there are other protections against it but still happens).
[0] https://github.com/appliedblockchain/tsql
[1] https://github.com/appliedblockchain/assert-combinators
-
Objection to ORM Hatred
Exactly. I'm happy with tsql [0] - template based, with safe sanitation, helper renderers/combinators, used in production for several years, would recommend this approach.
[0] https://github.com/appliedblockchain/tsql
-
DenoDB
Personally I prefer functional combinators like interfaces [0]. Js/ts have tagged templates which enhances those type of interfaces a lot. It gives access to full set of functionality of underlying database, not just common denominator of all used. It allows arbitrary compositions etc.
[0] https://github.com/appliedblockchain/tsql/
What are some alternatives?
trpc - 🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
denodb - MySQL, SQLite, MariaDB, PostgreSQL and MongoDB ORM for Deno
postgres - Postgres.js - The Fastest full featured PostgreSQL client for Node.js, Deno, Bun and CloudFlare
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
MySQL - A pure node.js JavaScript Client implementing the MySQL protocol.
typed-knex - A TypeScript wrapper for Knex.js
js-sqlate - A tiny tagged template string function library for JavaScript to write SQL safely. Works with Mapbox's SQLite3 library, Brian Carlson's PostgreSQL library and others.
PostgreSQL - PostgreSQL client for node.js.
node-sql-template-strings - ES6 tagged template strings for prepared SQL statements 📋