Re: proposal: ignore null fields in not relation type composite type based constructors - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: proposal: ignore null fields in not relation type composite type based constructors
Date
Msg-id 20140911122947.GA16422@tamriel.snowman.net
Whole thread Raw
In response to Re: proposal: ignore null fields in not relation type composite type based constructors  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: ignore null fields in not relation type composite type based constructors  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
* Pavel Stehule (pavel.stehule@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 :).
Thanks,
    Stephen

> 2014-09-08 6:27 GMT+02:00 Stephen Frost <sfrost@snowman.net>:
> > * Pavel Stehule (pavel.stehule@gmail.com) wrote:
> > > ignore_nulls in array_to_json_pretty probably is not necessary. On second
> > > hand, the cost is zero, and we can have it for API consistency.
> >
> > I'm willing to be persuaded either way on this, really.  I do think it
> > would be nice for both array_to_json and row_to_json to be single
> > functions which take default values, but as for if array_to_json has a
> > ignore_nulls option, I'm on the fence and would defer to people who use
> > that function regularly (I don't today).
> >
> > Beyond that, I'm pretty happy moving forward with this patch.

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [TODO] Process pg_hba.conf keywords as case-insensitive
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench throttling latency limit