| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add transforms feature |
| Date: | 2013-09-14 01:30:39 |
| Message-ID: | 1379122239.19286.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here is a new patch which addresses some of the issues you found.
> - vs SQL standard
>
After reviewing this, there is actually no conflict with the SQL
standard, because the CREATE TRANSFORM syntax in the SQL standard uses
an additional transform group clause which I don't use. So there is no
ambiguity. Hence, I left the syntax unchanged.
> - function types
I changed this so that CREATE TRANSFORM requires owning the from-SQL and
to-SQL functions.
> - create or replace causes inconsistency
>
Fixed this by adding cache invalidation in PL/Python.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Add-transforms-feature.patch | text/x-patch | 150.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-09-14 01:33:03 | Re: plpgsql.print_strict_params |
| Previous Message | Robert Haas | 2013-09-14 00:17:19 | Re: ENABLE/DISABLE CONSTRAINT NAME |