| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Hannu Krosing <hannu(at)krosing(dot)net>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json accessors |
| Date: | 2012-11-30 15:03:09 |
| Message-ID: | CAHyXU0zkDuYUN5S5ZTWpQ9rwuTcs8Q0A4WzemPTayreaBUmORA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 30, 2012 at 9:02 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 11/30/2012 09:51 AM, Merlin Moncure wrote:
>>
>>
>> Two questions:
>> 1) is it possible for these to work without a polymorphic object
>> passed through as hstore does (null::foo)?
>> select populate_record(anyelement, record, json)
>
>
> I don't understand the question. The API I'm suggesting is exactly in line
> with hstore's, which uses a polymorphic parameter. I don't see how it can
> not, and I don't understand why you would have 3 parameters.
my mistake: I misread the function as you write it. it's good as is.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2012-11-30 15:04:36 | Re: json accessors |
| Previous Message | Andrew Dunstan | 2012-11-30 15:02:16 | Re: json accessors |