mammoth
postgres
mammoth | postgres | |
---|---|---|
4 | 42 | |
492 | 6,722 | |
-0.2% | - | |
0.0 | 8.2 | |
7 months ago | 6 days ago | |
TypeScript | JavaScript | |
MIT License | The Unlicense |
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.
postgres
-
Neon Is Generally Available: Serverless Postgres
I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:
https://github.com/neondatabase/neon/issues/4989
If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.
Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.
To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?
-
Drizzle is just as unready for prime-time as Prisma, what else is there?
I'd push you to consider using postgres, slonik or similar for database queries. With these libraries, you just write SQL, but they perform input sanitization for you. So you can safely write:
- Ask HN: If you were to build a web app today what tech stack would you choose?
-
PostgresJs: The Fastest full featured PostgreSQL client for Node.js and Deno
Thanks Pier! Your comment saved me some frustration here :-D
https://github.com/porsager/postgres/discussions/627#discuss...
-
We migrated to SQL. Our biggest learning? Don't use Prisma ORM
There's a core client interface here:
- https://www.postgresql.org/docs/current/client-interfaces.ht...
On what makes it postgres.js faster, from author himself:
> it seems Postgres.js is actually faster than, not only pg, but of any driver out-there
- https://github.com/porsager/postgres/discussions/627
- https://porsager.github.io/imdbench/sql.html
-
Relational is more than SQL
When viewed as a DSL for set theory, views, CTEs, set-returning functions, et al are indeed proper first-class query abstractions.
When viewed through the lens of general purpose imperative or functional programming languages, it's easy to see how it can be seen as falling short.
I'll admit much of the tooling and driver APIs leave a lot to be desired.
Some tools do make good efforts though such as nested fragments in this driver.
https://github.com/porsager/postgres#building-queries
-
SQLite-based databases on the Postgres protocol? Yes we can
I don't think this should turn in to an ORM or not debate, but there are plenty of reasons, especially for the crowd that would do anything to avoid ORMs. Just try to take a peek into the multitude of "ORMs are bad" articles / discussions.
For instance - I would love to be able to use https://github.com/porsager/postgres with sqlite.
-
Is ORM still an anti-pattern?
Demonstrate how easily and accidentally one can make an SQL injection with these:
https://github.com/porsager/postgres
https://github.com/gajus/slonik
-
Storage on Vercel
They've looked at Postgres.js (https://github.com/porsager/postgres) before — wouldn't mind if they enabled those other cases in the same way.
What are some alternatives?
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
pg-promise - PostgreSQL interface for Node.js
Sqlmancer - Conjure SQL from GraphQL queries 🧙🔮✨
trpc - 🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
ucast - Conditions query translator for everything
rusqlite-model - Model trait and derive implementation for rusqlite
prisma-redis-middleware - Prisma Middleware for caching queries in Redis
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
MySQL - A pure node.js JavaScript Client implementing the MySQL protocol.
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
PostgreSQL - PostgreSQL client for node.js.