From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Nasty, propagating POLA violation in COPY CSV HEADER |
Date: | 2012-06-20 16:18:45 |
Message-ID: | 27682.1340209125@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter <david(at)fetter(dot)org> writes:
> OK, new proposal:
> COPY FROM (Thanks, Andrew! Must not post while asleep...) should have
> an option which requires that HEADER be enabled and mandates that the
> column names in the header match the columns coming in.
> Has someone got a better name for this option than
> KEEP_HEADER_COLUMN_NAMES?
Well, if it's just checking that the list matches, then maybe
CHECK_HEADER would do.
In your original proposal, I was rather wondering what should happen if
the incoming file didn't have the same set of columns called out in the
COPY command's column list. (That is, while *rearranging* the columns
might be thought non-astonishing, I'm less convinced about a copy
operation that inserts or defaults columns differently from what the
command said should happen.) If we're just checking for a match, that
question goes away.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John Lumby | 2012-06-20 16:24:53 | proposal and patch : support INSERT INTO...RETURNING with partitioned table using rule |
Previous Message | David Fetter | 2012-06-20 16:09:19 | Re: Nasty, propagating POLA violation in COPY CSV HEADER |