Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION

From: Daniel Farina <drfarina(at)gmail(dot)com>
To: Hannu Krosing <hannu(at)2ndquadrant(dot)com>
Cc: Daniel Farina <dfarina(at)truviso(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(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 08:57:02
Message-ID: 7b97c5a40911240057q4bbf9c7ldb5f1bac382c3f42@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 24, 2009 at 12:38 AM, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:
> COPY func(rowtype) FROM stdin;

I didn't consider rowtype...I did consider a type list, such as:

COPY func(typea, typeb, typec) FROM ...

Which would then operate just like a table, but be useless for the
data-cleaning case, and would not allow type overloading to be the
mechanism of selecting behavior.

It was just an idea...I don't really know the use cases well enough,
my anticipated used case was updating eagerly materialized quantities
with the UDF.

fdr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2009-11-24 09:46:56 Re: [HACKERS] Updating column on row update
Previous Message Daniel Farina 2009-11-24 08:54:26 Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION