pgocaml VS sqlc

I was looking around more and I found this OCaml library: https://github.com/darioteixeira/pgocaml

Although I haven't had to use it in several years, I'm quite fond of the OCaml extension I wrote which integrates PostgreSQL statements directly into the language. Values are type-checked across the boundary, SQL commands are validated at compile time, and proper prepared statements get generated (also at compile time). It's a little bit like MS Linq in concept, but it works by using PGSQL "DESCRIBE" to send the statement to the PostgreSQL server when compiling the code to do the validation and get the types. It really made writing database-baked websites less of a grind. https://github.com/darioteixeira/pgocaml

"Is there a way to get sqlc to use pointers for nullable columns instead of the sql.Null types?"

I came across this yesterday for golang: https://sqlc.dev which is somewhat like what you want, maybe.

Not sure it allows you to parameterize table names but the basic idea is codegen from sql queries so you are working with go code (autocompletion etc).

Agreed, but tools like https://sqlc.dev, which I mention in the article, are a good trade-off that allows you to have verified, testable, SQL in your code.

sqlc is not strictly a conventional ORM. It offers a unique approach by generating Go code from SQL queries. This allows developers to write SQL, which sqlc then converts into type-safe Go code, reducing the boilerplate significantly. It ensures that your queries are syntactically correct and type-safe. sqlc is ideal for those who prefer writing SQL and are looking for an efficient way to integrate it into a Go application.

I was browsing awesome-go for ideas on how to setup my data access layer when I stumbled on sqlc. It seemed like a great option. Code generation is a strategy often used in the Go ecosystem and making my queries safe at compile time was an idea I really liked. Knex was great, but it required of me that I test thoroughly my queries at runtime and that I sanitize my query results to ensure type safety within my application.

Now, we are going to generate the code. For this purpose, we are going to use sqlc.

https://github.com/sqlc-dev/sqlc — for use with //go:generate