Skip site navigation (1) Skip section navigation (2)

Re: json api WIP patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: json api WIP patch
Date: 2013-01-04 20:51:54
Message-ID: 50E740EA.3070903@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On 01/04/2013 03:36 PM, Pavel Stehule wrote:
> Hello
>
>
>
> 2013/1/4 Andrew Dunstan <andrew(at)dunslane(dot)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(at)dunslane(dot)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'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


In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2013-01-04 20:52:51
Subject: Re: Event Triggers: adding information
Previous:From: Pavel StehuleDate: 2013-01-04 20:36:07
Subject: Re: json api WIP patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group