| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Subject: | Re: [PATCH] Add transforms feature |
| Date: | 2013-11-26 22:08:58 |
| Message-ID: | 52951BFA.1000201@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/12/2013 12:21 PM, Peter Eisentraut wrote:
> A transform is an SQL object that supplies to functions for converting
> between data types and procedural languages.
How hard would it be to extend this to add transforms directly
between pairs of procedural languages ?
One example would be calling a pl/v8 function from pl/python
and converting directly between integers in both, without going
through PostgreSQL type.
Another and maybe even more interesting would be automatic
null-transforms between two pl/python functions.
Cheers
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-11-26 22:14:38 | doPickSplit stack buffer overflow in XLogInsert? |
| Previous Message | Bruce Momjian | 2013-11-26 22:02:02 | Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block |