Re: proposal: ignore null fields in not relation type composite type based constructors
От | Andrew Dunstan |
---|---|
Тема | Re: proposal: ignore null fields in not relation type composite type based constructors |
Дата | |
Msg-id | 5411C3E8.504@dunslane.net обсуждение исходный текст |
Ответ на | Re: proposal: ignore null fields in not relation type composite type based constructors (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: proposal: ignore null fields in not relation type composite type
based constructors
|
Список | pgsql-hackers |
On 09/11/2014 08:29 AM, Stephen Frost wrote: > * 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 :). 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. 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. cheers andrew
В списке pgsql-hackers по дате отправления: