Re: pl/python custom datatype parsers

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Jan Urbański <wulczer(at)wulczer(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-11-08 21:08:07
Message-ID: 4EB99A37.6040007@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/01/2011 11:50 AM, Peter Eisentraut wrote:
> On fre, 2011-02-11 at 16:49 +0100, Jan Urbański wrote:
>> I believe it's (b). But as we don't have time for that discussion that
>> late in the release cycle, I think we need to consider it identical to (c).
> As I previously mentioned, I think that there should be an SQL-level way
> to tie together languages and types. I previously mentioned the
> SQL-standard command CREATE TRANSFORM as a possibility. I've had this
> on my PL/Python TOTHINK list for a while. Thankfully you removed all
> the items ahead of this one, so I'll think of something to do in 9.2.
>
> Of course we'll be able to use the actual transform code that you
> already wrote.
>

Peter,

Did you make any progress on this?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2011-11-08 21:12:25 Re: Measuring relation free space
Previous Message Josh Berkus 2011-11-08 20:56:14 Releasing an alpha for CF2