On Thu, Sep 10, 2009 at 9:56 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Dimitri Fontaine <dfonta...@hi-media.com> writes: >> Last time we opened this can of worms here's what it lead us to: >> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00222.php > > Right, that's the discussion I was remembering. > >> As already said by Andrew on IRC, though, this goes nowhere to help him >> address his direct concern, COPY would still choke on input lines that >> are containing too few or too many columns... > > An easy fix for that is to allow this form of COPY to return text[] > instead of a fixed number of text columns.
Hmm... in fact, what if we just implemented COPY returning text[] for a first cut, and forget making it act like a table source for now. Then you could COPY to a temp table (with a text[] column) and select from there. There's really two separate features here: COPY producing text[] rather than a record type, and COPY being embeddable in some larger query. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
