Greg Brisebois

What if you could configure any generic type to wrap nulls? Something like: ```yaml go: ... generic_null_type: import: "my/custom/null" type: "Null" ... ``` and then a nullable `string` column would...

Put together an implementation of my above suggestion in #3202

This was fixed in 1.25.0 (https://github.com/sqlc-dev/sqlc/pull/3026), your playground example works when I update the version: https://play.sqlc.dev/p/a3eacaca248da3c046efd82fca0056dd995a9a8eac903d5f8eb3117cf14cce84

I'm not supper happy about how this works (or rather doesn't work) with overrides. Ideally I would specify a custom override type without specifying its nullability, and then with this...

Superseded by #3279

Thoughts on an option for setting `omitempty` on nullable fields only? Slightly more of a pain to implement since `JSONTagName` doesn't know the nullability of its field.

1. In responses I figured `null` is more explicit for values that are null in the DB for example, as opposed to being "not required". If this is not what...

Looks like `nullable` was removed from 3.1: https://github.com/OAI/OpenAPI-Specification/issues/2244#issuecomment-899084964 Edit: also https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0

It seems that to support the 3.1 way of doing nulllable: ```yaml type: - "string" - "null" ``` then `Schema.Type` would need to be a slice instead of a string,...

That does do the trick, thanks! Last question: is it possible to make it do this by default for native pointer types? Right now, a Go `*string` is represented as...