newtype-ts VS pgtyped

Curious what your issue was with duck-typing. Were you effectively looking to create ADTs that are required to go through a specific step-by-step process, not simply 'look like' the thing that was expected?

If so, you might be interested in [newtype-ts].

[newtype-ts]: https://github.com/gcanti/newtype-ts

this one https://github.com/gcanti/newtype-ts ?

You don't need classes for nominal types: https://github.com/gcanti/newtype-ts

Creating newtypes (via newtype-ts) for fractions and percentages is worthwhile if you're very concerned about correctness, though it's unfortunate that absent typeclasses they're not terribly ergonomic.

I haven't used this library in particular or this one, but bless the authors and all the others for trying to make it happen… the project I'm now leading uses strongly typed strings for different component addresses, and it saves me to constantly look up the documentation what the functions need – it's beautiful.

A "nominal" solution with no runtime overhead can be provided by branded types, other words for this are "opaque types" or "newtypes". Some libraries like newtype-ts exist to help with the construction of these. That library README describes it as:

You can also look at the fp-ts ecosystem for inspiration. newtype-ts and io-ts's Branded type with io-ts-type's UUID as a good example

Alternatively we can use other more sophisticated techniques to achieve nominal typing or libraries such as: newtype-ts or io-ts.

One using fp-ts and newtype-ts

We are going to use newtype-ts to build a branded type:

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!