pgtyped VS @databases

There is an implementation of SQL that operates on a table shaped type, entirely at type level. For your amusement: https://github.com/codemix/ts-sql

There are a bunch of more practical takes that codegen types from your database and generate types for your queries, eg: https://github.com/adelsz/pgtyped

To me the second approach seems much more pragmatic because you don’t need to run a SQL parser in a fairly potato interpreter on every build

ORMs suck, but raw SQL embedded in your code sucks too.

This might be good time to plug my TypeScript non-ORM: https://jawj.github.io/zapatos/.

I should say I also like what I've seen of https://kysely.dev/ and https://pgtyped.dev/.

Thank you for suggestions they helped me finding what I was looking for. I will either pick kysely or https://pgtyped.dev/, but first I will do some tests. Thanks!

Cool. How does this compare to SafeQL, PgTyped, and Postgres language server ?

I would instead rely on code generation like https://github.com/adelsz/pgtyped, because the embedded type-safe SQL will never fully cover all the features of vanilla SQL, for example Common Table Expression (CTE), window functions etc.

There's pgtyped, which I believe does almost the same as sqlc

https://github.com/adelsz/pgtyped

For Postgres there is https://github.com/adelsz/pgtyped, sounds pretty much like what you describe?

Avoiding the cost of learning EDSL that many Haskell DB libraries provide, I found out that only postgresql-typed and postgresql-simple allow to write only raw SQL queries easily. As I extensively use pgtyped for production Node.js application, I am thinking about using postgresql-typed. While I could find many resources for postgresql-simple, the same cannot be said try for postgresql-typed.

I would highly recommend trying out pgTyped if you want typesafe queries with postgres. It's fantastic!

At Databases because you don't need ORM.

Depending on the complexity of your queries, Prisma might indeed not be the best abstraction for you. If you're proficient in SQL and don't want to sacrifice type-safety, there are really nice, low-level alternatives to Prisma such as Zapatos, Slonik or atdatabases. We're laying this out in our docs here: Should you use Prisma?

I built https://www.atdatabases.org to make this as easy as possible to get right when querying SQL databases with node.js

Depends a lot on the size of your database records. We’ve found that for a few tables with big JSONB columns it can make a huge difference but for 90% of queries it makes very little difference. https://www.atdatabases.org with @databases/pg-typed or @databases/mysql-typed also keeps the types in sync with which columns you select.

Since the method is marked as async, you can use await to get the results of a query (if your database library supports promises. For example with https://www.atdatabases.org as your db library you could do

I found Prisma close but not quite there. That's part of what motivated me to keep working on https://www.atdatabases.org, which I think is already there as an enterprise ready ORM for node.js

I built https://www.atdatabases.org which has an ORM for node.js, but also supports writing SQL queries in a safe way. It is type safe, and has much simpler & more flexible transaction support than most node.js ORMs.

If you’re using TypeScript and don’t have untrusted user data, @databases can generate static types, which can be a good alternative to runtime validation.

Did either of you consider @databases? It has pretty much the same approach to SQL as Slonik. I’m curious if there’s any reason why Slonik is preferable?