Re: pl/python custom datatype parsers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pl/python custom datatype parsers
Date: 2011-02-11 15:43:49
Message-ID: AANLkTinT6QPE5TefXws2Px80Au_JD7nhZimtwV4MVRY_@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Feb 6, 2011 at 1:01 PM, Jan Urbański <wulczer(at)wulczer(dot)org> wrote:
>> That's it for now. It is an exciting feature and plpython will be the
>> first language to think of when you're building "object database" if
>> this feature is in. The design here will affect following pl/perl and
>> other so it is important enough to discuss.
>
> Yes, I ended up writing this patch as a PoC of how you can integrate
> procedural languages with arbitrary addon modules, so it would be good
> to have a discussion about the general mechanisms. I'm aware that this
> discussion, and subsequently this patch, might be punted to 9.2
> (although that would be a shame).

It's not clear to me from this discussion whether this patch (a) now
works and has consensus, and should be committed, (b) still needs more
discussion, but hopes to make it into 9.1, or (c) is now 9.2 material.

Can someone please clarify?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2011-02-11 15:45:00 Re: REVIEW: Determining client_encoding from client locale
Previous Message Robert Haas 2011-02-11 15:39:26 Re: REVIEW: Determining client_encoding from client locale