Re: COPY Transform support - Mailing list pgsql-hackers

From Tom Lane
Subject Re: COPY Transform support
Date
Msg-id 15798.1207252658@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPY Transform support  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: COPY Transform support  (Andrew Dunstan <andrew@dunslane.net>)
Re: COPY Transform support  (Sam Mason <sam@samason.me.uk>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> AFAIK the state of the art is actually to load the data into a table which
> closely matches the source material, sometimes just columns of text. Then copy
> it all to another table doing transformations. Not impressed.

I liked the idea of allowing COPY FROM to act as a table source in a
larger SELECT or INSERT...SELECT.  Not at all sure what would be
involved to implement that, but it seems a lot more flexible than
any other approach.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Brendan Jurd"
Date:
Subject: Re: Separate psql commands from arguments (was: psql command aliases support)
Next
From: David Fetter
Date:
Subject: Re: psql \G command -- send query and output using extended format