Adel Salakh

> This is too naive actually, as it affects the result types too rather than **just** parameter types. I'll need to re-think the approach. Yes, maybe it can be added...

Hi @goofiw, Type overrides weren't ever completely implemented. As you noticed, the core TypeAllocation data structures do support overrides and external file imports, but all of that functionality isn't exposed...

> I was thinking a path to an pgtyped.overrides.ts file might be more extendable - I'm doing some geometry functions as well that would be cool to define types for....

Generation templates are neat. A good first step is to extract the current string interpolation logic (`cli/src/generator.ts` and `cli/src/index.ts`) into a standalone template file. We can then provide the option...

Hey @FrigoEU, Unfortunately there isn't much we can do about this atm, this seems to be a bug in the postgres type inference engine.

I think adding parsers is a step in the right direction. Initially I planned for PgTyped to be a mostly compile-type library, but can see how it can be much...

JSON aggregates are quite powerful, but unfortunately they are untyped as is. I do like the idea of introducing a special json keyword that would run type interference on all...

That does look like inconvenient. I think a good way to solve this is to introduce a "required" spread parameter syntax. Queries that include such parameters should fail if one...

This has been fixed as part of our migration to ESM.

Basic type overrides have now been added. Imported type overrides are in the work as part of https://github.com/adelsz/pgtyped/issues/480