From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)krosing(dot)net> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Farina <dfarina(at)truviso(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
Date: | 2009-11-24 10:10:48 |
Message-ID: | 162867790911240210n1f95eca8g26bc6b7d9ca89245@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
I thing, so this patch is maybe good idea. I am missing better
function specification. Specification by name isn't enough - we can
have a overloaded functions. This syntax doesn't allow to use explicit
cast - from my personal view, the syntax is ugly - with type
specification we don't need to keyword FUNCTION
what about::
var a) by type specification
COPY table TO foo(varchar, int)
var b) by value expression - it allows some changes in order, casting, constants
COPY table TO foo($3, $1::date, $2::text, CURRENT_DATE, true);
One question:
We have a fast copy statement - ok., we have a fast function ok, but
inside a function we have to call "slow" sql query. Personally What is
advantage?
We need pipes like
like COPY table TO foo(..) TO table
foo() should be a transformation function, or real pipe function
Regards
Pavel Stehule
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-11-24 10:15:53 | Re: Partitioning option for COPY |
Previous Message | Thom Brown | 2009-11-24 09:46:56 | Re: [HACKERS] Updating column on row update |