| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new json funcs |
| Date: | 2014-01-27 17:43:12 |
| Message-ID: | CAHyXU0ysQ+W=gaSr1nXTK30vYU-X1hvy4mb06=Zy_L-Ujd6oTQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 24, 2014 at 3:26 PM, Josh Berkus <josh(at)agliodbs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-01-27 17:44:41 | Re: A better way than tweaking NTUP_PER_BUCKET |
| Previous Message | Stephen Frost | 2014-01-27 17:40:45 | Re: A better way than tweaking NTUP_PER_BUCKET |