From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY with column headings |
Date: | 2004-08-16 18:41:03 |
Message-ID: | 4120FFBF.2020907@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>
>>>I certainly think it's worth considering, although I see Tom has
>>>objected :-) . Say we have an option called FIRSTLINELABELS, then on
>>>copy out it would write the headings on the first line, and on copy in
>>>it could just ignore the first line (so it could work symmetrically).
>>>
>>>
>
>
>
>>Yes, that is what I was thinking. Is this a TODO? Sure it can be
>>misused but most copy options can be similarly misused.
>>
>>
>
>Most copy options will result in obvious failures if misused. I dislike
>this one because of the high risk of silent corruption of your data
>(loss of a row or insertion of a row that shouldn't be there).
>Considering no one has even made a positive case why we should add it
>(for instance, a use-case where it's necessary), I don't think it
>belongs in the to-do list.
>
>
>
>
The use case is that it fits in with the way spreadsheets usually do
data tables, and many will only allow you to export a whole worksheet
(including the heading row) to CSV, not a part of one. Conversely,
working with imported data tables will be harder if they lack headings.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-16 19:04:13 | Re: COPY with column headings |
Previous Message | Merlin Moncure | 2004-08-16 17:12:37 | Re: Open items |