squeal-postgresql VS beam

You may want to have a look at squeal that someone mentioned the other day in the comments of this post.

https://github.com/morphismtech/squeal, because, to my knowledge, it's the only option that both maintains deep type safety without losing the expressive power of SQL. It can even typecheck your database migrations. There's even a tool to generate the types of your schema based on an existing database: https://github.com/mwotton/squealgen

Yep, https://github.com/morphismtech/squeal does this too.

If you want an example of a type-safe SQL eDSL in Haskell that doesn't have those problems (and supports more Postgres features than esquelto), I'd recommend https://github.com/morphismtech/squeal.

I'm not familiar with GPUs specifically, but I have seen this for ORMs that support multiple SQL dialects (e.g. [0]).

A great technique is called 'tagless final encoding' [1]. Using this technique, you can specify capabilities of an embedded domain-specific language (eDSL) such that you can have a shared (but narrow) common set of features, while allowing specializations of this eDSL to support extra features.

[0]: https://github.com/haskell-beam/beam

[1]: https://nrinaudo.github.io/articles/tagless_final.html

https://haskell-beam.github.io/beam/ is fantastic, but good luck understanding it if you don't already know some Haskell

Beam “is a highly-general library for accessing any kind of database with Haskell”. Beam makes extensive use of GHC's Generics mechanism — no Template Haskell.

One anecdotal opinion from a rando reddit user: I prefer beam despite the boilerplate and more complex types because of the authors make a serious attempt at sql-standards compliance: https://github.com/haskell-beam/beam

It's actively worked on: https://github.com/haskell-beam/beam Makes heavy use of the type level though.

The beam library is one example of this: https://github.com/haskell-beam/beam/pulls