| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSON Function Bike Shedding |
| Date: | 2013-02-14 21:39:43 |
| Message-ID: | CAHyXU0x5GkSejBPZ1p3O7Et4Vwj7dqr6=ir51Cdov99hO5xH0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 13, 2013 at 11:40 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Andrew Dunstan wrote:
>>
>> On 02/13/2013 12:07 PM, David E. Wheeler wrote:
>> >On Feb 13, 2013, at 8:36 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>> >>I think Merlin's suggestion if unwrap might be good. Or simply "elements()" might work.
>> >Perhaps unwrap() returns a set and elements() returns an array?
>>
>> Now you're adding functionality. Let's just keep this to the
>> question of names.
>
> I agree with that, but it seems a good idea to leave names available for
> future functionality, where reasonable.
Given all that, is there consensus on the names so that Andrew knows
what changes to make?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2013-02-14 22:48:48 | Re: Call for Google Summer of Code mentors, admins |
| Previous Message | Sîrbu Nicolae-Cezar | 2013-02-14 21:38:18 | Re: [pgsql-advocacy] Call for Google Summer of Code mentors, admins |