| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Joe Van Dyk <joe(at)tanga(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Why doesn't COPY support the HEADER options for tab-separated output? |
| Date: | 2013-08-12 22:17:00 |
| Message-ID: | CAMkU=1yZ2ARKT1aT3NF-SJXv6gKBrP7bBprLAyZrLUFyv1JhGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 12, 2013 at 2:21 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, Aug 12, 2013 at 02:15:25PM -0700, Joe Van Dyk wrote:
>> Mostly just curious, as this is preventing me from using tab-separated output.
>> I'd like there to be a header in my files. I have to use CSVs instead.
>
> [ "this" means the fact that COPY doesn't support the HEADER option. ]
>
> We assume CSV is going to be read into a tool that can use the header
> names; delimited files don't usually have a use for those headers.
There have been a few cases where I wanted this, too. I can see why
implementing it is less important than having it for CSV, but is there
a reason to consider this harmful for TEXT format? I.e. if someone
submitted a patch, would it be rejected?
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-12 22:18:16 | Re: Why doesn't COPY support the HEADER options for tab-separated output? |
| Previous Message | Merlin Moncure | 2013-08-12 22:05:42 | Re: Why doesn't COPY support the HEADER options for tab-separated output? |