Kyle Gray

Hey there! I maintain github.com/sqlc-dev/sqlc. For some query analysis work I'm doing I need more of the metadata provided by the server. I'm not sure if this is of any...

I updated the title and added the tag we use for all new engine requests. This one is unlikely to happen soon, mainly because I have larger plans for refactoring...

I posted a [2026 roadmap](https://github.com/sqlc-dev/sqlc/discussions/4204) a few days ago. While this didn't make it, the Go API should make it much easier to support SQL Server. @twolfvb the help I...

A workaround that we haven't discussed is using `sqlc.narg`. ```sql -- name: UpdateAuthor :exec UPDATE authors SET name=COALESCE(sqlc.narg(name), name) WHERE id=$1; ``` PostgreSQL itself treats all query parameters as nullable....

It's an interesting idea. We've kicked around generating different interfaces for reader and writers, but that wouldn't solve your issue as you're preparing the queries before hand. The best I...

Can you include the table definition for `country_types`?

@ignat980 if you open this against main I can get this merged. Just make sure to includes Andrew's commits.

@asmyasnikov appreciate the effort here! Right now supporting the three existing database engines is challenging enough. I have some longer term plans on making that easy, but in the meantime,...

FDWs are currently not supported. I'm working on adding support for a database-only analyzer which should work well with FDW and other advanced PostgreSQL features.