Steven Kabbes

I added the env var, and get this next error message. ``` ➜ wasm_plugin_sqlc_gen_greeter git:(catalog_tables_views) ✗ WASMTIME_BACKTRACE_DETAILS=1 sqlc-dev generate # package greeter error generating code: loadModule: Module was compiled without...

@kyleconroy given [this commit](https://github.com/kyleconroy/sqlc/pull/1748/commits/e2c0a7549e34e7df4ecdd9935c4d8b820839fd1d) fixed the build, I think it has something to do with the pure size of the data or number of tables in pg_catalog. I believe since...

No, sorry I didn't explain well. _routines_ in Postgres can be regular functions, procedures, aggregates, and window functions. https://www.postgresql.org/docs/current/catalog-pg-proc.html If it is an aggregate, there are 2 kinds of arguments,...

I think this: https://github.com/kyleconroy/sqlc/pull/1809 Is the first step in actually making progress here.

I islolated the pg_* fixes in this PR: https://github.com/kyleconroy/sqlc/pull/1811 I think the "aggreagated function args vs direct args" can / should be addressed independently.

Ah, I hit this bug too - and coincidentally found the same workaround.

I think this is an endless game of whack-a-mole. I _think_ in general type-checking is impossible, take for example: ```sql select sqlc.arg('string_or_float')::int as x ``` how can sqlc know what...

I believe since there is no ambiguity in interpreting numbers as columns vs values, there is no problem with either approach.

@nickjackson I know I'm late to the party here, so apologies in advance. First off, this is a very cool piece of functionality, and I am in particular interested if...

> I think your suggestion should be an additional feature, not a replacement and I'll explain why With you explanation (and the fact that sqlc wants to be multi-database), I'm...