Re: new json funcs - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: new json funcs
Date
Msg-id CAHyXU0ysQ+W=gaSr1nXTK30vYU-X1hvy4mb06=Zy_L-Ujd6oTQ@mail.gmail.com
Whole thread Raw
In response to Re: new json funcs  (Josh Berkus <josh@agliodbs.com>)
Responses Re: new json funcs  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Fri, Jan 24, 2014 at 3:26 PM, Josh Berkus <josh@agliodbs.com> wrote:
> On 01/24/2014 12:59 PM, Andrew Dunstan wrote:
>>
>> On 01/24/2014 03:40 PM, Laurence Rowe wrote:
>>> For consistency with the existing json functions (json_each,
>>> json_each_text, etc.) it might be better to add separate
>>> json_to_record_text and json_to_recordset_text functions in place of
>>> the nested_as_text parameter to json_to_record and json_to_recordset.
>>>
>>>
>>
>> It wouldn't be consistent with json_populate_record() and
>> json_populate_recordset(), the two closest relatives, however.
>>
>> And yes, I appreciate that we have not been 100% consistent. Community
>> design can be a bit messy that way.
>
> FWIW, I prefer the parameter to having differently named functions.

+1.

merlin



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: A better way than tweaking NTUP_PER_BUCKET
Next
From: Pavel Stehule
Date:
Subject: Re: A better way than tweaking NTUP_PER_BUCKET