Gabriel Nordeborn

Useful to regenerate when DB changes.

For many projects, https://pglite.dev/ looks like it could be a good alternative for driving the typegen without having to host and connect to an actual Postgres DB. Worth exploring.

We've started diverging enough from `pgtyped` to actually drop the efforts of keeping this an actual fork. Plus, `pgtyped` is not actively developed anymore. So, I think we can unwind...

Might be nice to make it easy to autogenerated CRUD operations. Unclear however if this should just be tooling that generates the query for you, that you can then edit...

The current parser we use is great, but covers only parts of the Postgres syntax, and I've already hit limitations around that. https://github.com/pg-nano/pg-parser

https://github.com/zth/pgtyped-rescript/pull/14 added inference for `json_populate_recordset` and friends. There are a bunch of other JSON functions that dictate the JSON structure expected that we could infer in the same way.

Make sure it works in: * Input params

[PoC] Allowing ad hoc aliasing of an or pattern of literals into a polyvariant

1

Now that the runtime represenation of polyvariants is stable and well defined, we can allow aliasing or patterns of literals into a polyvariant if we want, since we can guarantee...