2013/1/4 Andrew Dunstan <andrew@dunslane.net>:
>
> On 01/04/2013 03:36 PM, Pavel Stehule wrote:
>>
>> Hello
>>
>>
>>
>> 2013/1/4 Andrew Dunstan <andrew@dunslane.net>:
>>>
>>> On 01/02/2013 05:51 PM, Andrew Dunstan wrote:
>>>>
>>>>
>>>> On 01/02/2013 04:45 PM, Robert Haas wrote:
>>>>>
>>>>> On Wed, Dec 26, 2012 at 3:33 PM, Andrew Dunstan <andrew@dunslane.net>
>>>>> wrote:
>>>>>>
>>>>>> Here is a patch for the first part of the JSON API that was recently
>>>>>> discussed. It includes the json parser hook infrastructure and
>>>>>> functions
>>>>>> for json_get and friends, plus json_keys.
>>>
>>>
>>>
>>> Udated patch that contains most of the functionality I'm after. One piece
>>> left is populate_recordset (populate a set of records from a single json
>>> datum which is an array of objects, in one pass). That requires a bit of
>>> thought.
>>>
>>> I hope most of the whitespace issues are fixed.
>>>
>> it is looking well
>>
>> I have one note - is it "json_each" good name?
>>
>
>
> Possibly not, although hstore has each(). json_unnest might be even less
> felicitous.
I understand - but hstore isn't in core - so it should not be precedent
regexp_split_to_table
I am not native speaker, it sounds little bit strange - but maybe
because I am not native speaker :)
Regards
Pavel
>
> I'm expecting a good deal of bikeshedding - I'm trying to ignore those
> issues for the most part because the functionality seems much more important
> to me than the names.
>
> The more people that pound on it and try to break it the happier I'll be.
>
> cheers
>
> andrew