Re: How hard would a "path" operator be to implement in PostgreSQL

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
Cc: Chris Travers <chris(dot)travers(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: How hard would a "path" operator be to implement in PostgreSQL
Date: 2012-08-23 19:20:02
Message-ID: CAHyXU0xGf6RtA-62Kj=MTiVMqe9tysiThGwXhXi=rRe6UYCwQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 21, 2012 at 2:56 AM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:
> On 08/21/2012 03:01 PM, Martijn van Oosterhout wrote:
>>
>> Well, Postgres in principle supports arrays of records, so I've
>> wondered if a relationship join could stuff all the objects in a single
>> field of the response using an aggregate. I think what's always
>> prevented this from working is that client would have to parse the
>> resulting output text output, which is practically impossible in the
>> face of custom types.
>
>
> That's where the new JSON support is interesting; it provides a much more
> commonly understood and easier to parse structured form for results, so
> trees (but not more general graphs) can be returned.

I'd go beyond 'interesting' and call it a complete game changer if you
are consuming data in a language that has good support for JSON
(especially javascript naturally). Another good option if you're
consuming structured data in C is libpqtypes.

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2012-08-23 19:36:58 Re: Some thoughts on table inheritance (which is uniquely awesome on PostgreSQL)
Previous Message Jeremy Palmer 2012-08-23 19:12:55 Windows SIngle Sign On - LINUX Server