You can easily create a type that embeds sql.Null* and make that type implement all the Marshallers and Unmarshallers that you need. Or, if you only need json and don't want to write any additional code, you can the null package to handle this for you.

Hi @euller88, what do you suggest in case I do not want interface to have sql specific types. As there might be other nosql implementation

@dharmjit I do not know what to do, but I have a suggestion. Try to override every type you expect to receive to either interface{} or map[string]interface{}. But remember that this is a really bad suggestion. If you really want to use the data between a relational and a nosql databases, you should write some conversion code.

I think a perl one-liner to replace sql.NullString with *string is the way I'm going to go, no intermediate steps or extra code needed.

But thats just me, I'm still really impressed with the utility of sqlc and wish I had something like this twenty years ago.

I would very much like for this to be a feature as well. Happy with sqlc in many ways, good work.

For anyone reading this thread, I added the following to my Makefile:

sql:
	sqlc generate
	sed -i -e 's/sql.NullString/*string/g' pkg/queries/*.go
	sed -i -e 's/sql.NullInt32/*int32/g' pkg/queries/*.go
	sed -i -e 's/sql.NullTime/*time.Time/g' pkg/queries/*.go
	goimports -w ./pkg/queries/

Will probably be solved by #1571.