kirk-anchor

The string conversion bug has now been fixed in `pgtype.Numeric` so `--go-type 'numeric=string'` can be used as a workaround to allow using `numeric` columns in composite types

It would be great to have pgxv5 support. Batch queries are not essential to me but composite types are. I considered switching to sqlc for pgxv5 support but its lack...

Support for composite types of a TABLE/TYPE would be great. A further improvement would be supporting arbitrary record types that don't belong to a TABLE/TYPE if that would be possible....

I have queries that use `jmoiron/sqlx` so I cannot use `pgtype.Map.SQLScanner` on arrays. I was previously using the type specific array structs on pgx-v4. I managed to workaround the issue...