Tejas Mehta

@keeshux Couldn't find any issues in local tests against VPN servers

Ah alright, thanks for letting me know! Would you mind letting me know what the perf testing looked like? I'd love to reproduce it on my end to see the...

@porsager Should be updated for all tests and in the main source directory. The changes made essentially check if existing known type mappings exist and cut the round trip used...

@porsager Benchmarks look like the fluctuate between this implementation and the existing implementation, so I don't see a visible constant difference on my end. EDIT: Removed the log I missed,...

@porsager If I understand #392 correctly, it allows explicit definitions of types or inference from postgres, so in the case where all types in a query are explicitly defined, this...

Ah makes sense. What was the conversation about the user explicitly specifying a type? would that be mapped prior to receiving the `ParameterDescription` message?

In that case then, where no inference is needed, would there still be a need to receive information from the `ParameterDescription` response? If not, then this should still apply so...

@porsager Ah my bad, I misunderstood then. I'd still be in favor of merging this PR for now as it seems like the JS inference will take a while to...

Bump on this, using nestJS currently doesn't allow me to generate methods returning a promise

@alexkb I see the types be promise or observable for the controller implementations but the clients only have observable in the definitions, not sure why that is. I have the...