prisma-kysely VS PostgreSQL

You can just use prisma for migrations. check out prism-kysely

I typed up a comment saying how much I’d love to drop this in alongside my Prisma code so I can keep using the ORM for simple things and have the option to drop into SQL as needed. It ended asking if anyone knew whether such a thing was possible. I decided to check the docs one more time and… here it is! https://github.com/valtyr/prisma-kysely

I’m excited. I enjoy Prisma but SQL can be expressive. Looking forward to trying this.

You can use Prisma for schema management and migrations, while using Kysely for query building and execution (check out https://github.com/valtyr/prisma-kysely). This is especially great in FaaS where Prisma is causing people trouble.

pg doesn't do too well with serverless, dead connections are left in the pool (or something)

https://github.com/brianc/node-postgres/issues/2112

If you don't want to use ORM then there are some other packages as well! For PostgreSQL we have node-postgres

Interface with PostgreSQL database

(Instead of the following with pg.)

So far every JS framework that uses https://node-postgres.com works great and so no reason to think Drizzle wouldn't.

One thing that keeps coming up is that SQL equals low productivity. I don't think this is true. I think the culprit is that most developers are using to heavily abstracting SQL using ORMs like Prisma that hides the database and SQL logic.

Since building a SQL generator (https://aihelperbot.com) as a side project, I have become much more proficient in SQL and even though I am also locked into Prisma, I use the `queryRaw` all the time to execute raw SQL queries. You can understand the code without knowing Prisma API. It is more performant. For more complex SQL queries, I use the SQL generator for initial suggestions and adapt if needed.

For the next projects I build I want to use the minimal Postgres client (https://github.com/brianc/node-postgres) combined with a lightweight migration library.

For newer projects I use the small Postgres client. Initially my leap into SQL was lead by AI but as I refreshed and relearned SQL, I now use a mixture of AI and self-written SQL queries. Something like this is just easier to have AI do the grunt work and then adjustment as needed.

This was a known issue for pg developers, and they managed to fix it a long time ago (at the pg level), but the knowledge of this problem didn't reach Knex maintainers.

Integrate the database into your application itself with a postgres client library allowing your applications to make infrastructure changes (like provisioning sharded resources for a client that wants isolation, or using a more accurate forecasting model to pre-allocate more resources before the storm hits).

node-postgres (raw sql, without ORM)