Andrew, * Andrew Dunstan (and...@dunslane.net) wrote: > On 09/11/2014 08:29 AM, Stephen Frost wrote: > >* Pavel Stehule (pavel.steh...@gmail.com) wrote: > >>Can I help with something, it is there some open question? > >I had been hoping for a more definitive answer regarding this option for > >array_to_json, or even a comment about the change to row_to_json. > >Andrew- any thoughts on this? (that's what the ping on IRC is for :). > > The change in row_to_json looks OK, I think. we're replacing an > overloading with use of default params, yes? That seems quite > reasonable, and users shouldn't notice the difference.
Right. Great, thanks.
> There might be a case for optionally suppressing nulls in
> array_to_json, and it might work reasonably since unlike SQL arrays
> JSON arrays don't have to be regular (if nested they are arrays of
> arrays, not multi-dimensional single arrays). OTOH I'm not sure if
> it's worth doing just for the sake of orthogonality. If someone
> wants it, then go for it.
Ok. I'll handle updating both of these to remove the overloading
and use default params instead, but I'll only add the 'ignore_null'
option to row_to_json.
Thanks again!
Stephen
signature.asc
Description: Digital signature
