Marshaling data into sql.NullString about xo HOT 4 CLOSED

Is there any way to change sql.NullString to *string? I use pointers to deal with null values as it is the cleanest solution.

from xo.

No, not at the moment. I am in the middle of planning for a large (almost total) rewrite of xo, and there has been a lot of requests in general for better ways to specify / override the types that xo generates. As such, in the future I envision there will be significantly better ways to provide these options to xo in the future. At the moment, I would just suggest building your own, modified version locally and using that instead. Changing specific types for a database is relatively easy/straightforward, simply modify the appropriate loader for your database (in the loaders directory).

from xo.

This isn't really an issue with xo -- you would have this problem no matter the way you chose to generate (or manually wrote) types for your models. Unfortunately, the json.Marshal and json.Unmarhsal aren't directly compatible with the sql.Null<Type> types.

You could write the json.Marshaler and json.Unmarshaler interfaces for the model types that would work with the types generated by xo. If you do, you could add that to the xo template.

It should be noted that directly marshaling a JSON type into a database model is a bad idea for non-trivial applications.

from xo.

Thanks for your quick response and suggestions. I've wound up instead adding NOT NULL DEFAULT '' to the various varchar/text fields. So, xo now casts them as string, rather than sql.NullString, which works great for what I wanted.

from xo.