| From: | Chris Travers <chris(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: json_populate_record and nested json objects |
| Date: | 2013-09-16 00:13:49 |
| Message-ID: | 1720654706.211305.1379290429511.open-xchange@email.1and1.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 15 September 2013 at 18:42 Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
>
> On 09/14/2013 10:27 PM, chris travers wrote:
>
> Well, you could fairly easily build it as an extension as a POC. The
> main point of the API this is built on was to allow for extensions.
>
> The logic changes might be a bit tricky. I'll be interested to see what
> you come up with.
>
> If we're going to do this we should make these handle arrays as well as
> objects.
Yes, arrays are necessary for my use case. I probably should have been explicit
that I needed that too.
Best Wishes,
Chris Travers
>
> cheers
>
> andrew
>
>
Best Wishes,
Chris Travers
http://www.2ndquadrant.com
PostgreSQL Services, Training, and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Satoshi Nagayasu | 2013-09-16 04:20:52 | Re: [PoC] pgstattuple2: block sampling to reduce physical read |
| Previous Message | Ian Lawrence Barwick | 2013-09-16 00:11:56 | Re: Commitfest II, 9.4 edition |