mammoth
rusqlite-model
| mammoth | rusqlite-model | |
|---|---|---|
| 4 | 1 | |
| 492 | 11 | |
| -0.2% | - | |
| 0.0 | 0.0 | |
| 7 months ago | over 1 year ago | |
| TypeScript | Rust | |
| 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.
mammoth
-
PostgresJs: The Fastest full featured PostgreSQL client for Node.js and Deno
Super happy user of this [1] it's rather minimalistic but great.
[1] https://github.com/Ff00ff/mammoth
- Mammoth: A type-safe Postgres query builder pur sang for TypeScript
-
Kysely — A type-safe SQL query builder for typescript
This looks awesome. I had previously used Mammoth, but will dig into your library this weekend. Great job!
-
Show HN: Write universally accessible SQL, not library-specific ORM wrapper APIs
In a type-safe environment I think you should just be able to switch your pur sang SQL builder to another dialect. Because of the type-safety you’ll be able to find incompatibilities at compile time which makes the migration easy enough (ignoring data migration). This avoids creating a weird ad hoc SQL dialect trying to fit all the others in a single API.
I work on Mammoth which is a pur sang Postgres query builder, see https://github.com/Ff00ff/mammoth.
rusqlite-model
-
Show HN: Write universally accessible SQL, not library-specific ORM wrapper APIs
I'm quite anti-ORM, though I've never not used one professionally (just because it's already been there / not my decision), so that might be different if I did for a while. I do think something's necessary though, and it maybe is a bit arbitrary where we draw the line for what's an 'ORM'?
For example, I really enjoyed using rusqlite for a little side project/personal thing, but found apart from anything else just the repetition of `(?,?,?,?,?,?)` any time I wanted to insert something was annoying, for example. I started working a bit on [0] .. I don't know if I'd call it an ORM, just so I didn't have to do that, and could write `Model { ... }.insert(&conn)` instead. But still write plain SQL queries, I just want easy mapping between db table and language 'model' struct/class; column and field/attr.
[0] - https://github.com/OJFord/rusqlite-model
What are some alternatives?
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
diesel - A safe, extensible ORM and Query Builder for Rust
Sqlmancer - Conjure SQL from GraphQL queries 🧙🔮✨
pure-orm - A pure ORM for writing native SQL queries yielding pure business objects
ucast - Conditions query translator for everything
pgdbf - Convert XBase / FoxPro databases to PostgreSQL
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Norm - The SQL generation library you already know how to use.
pitwall-pg - A postgres library to help write safe, parameterized, transaction-aware SQL for when an ORM or query builder isn't the right tool for the job
rbatis - Rust Compile Time ORM robustness,async, pure Rust Dynamic SQL