Re: Nasty, propagating POLA violation in COPY CSV HEADER
От | Tom Lane |
---|---|
Тема | Re: Nasty, propagating POLA violation in COPY CSV HEADER |
Дата | |
Msg-id | 27682.1340209125@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Nasty, propagating POLA violation in COPY CSV HEADER (David Fetter <david@fetter.org>) |
Ответы |
Re: Nasty, propagating POLA violation in COPY CSV HEADER
Re: Nasty, propagating POLA violation in COPY CSV HEADER |
Список | pgsql-hackers |
David Fetter <david@fetter.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
В списке pgsql-hackers по дате отправления: