From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
Cc: | Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: COPY statement: no list of the allowed values for "format_name" |
Date: | 2020-10-30 00:22:16 |
Message-ID: | CAKFQuwbiaftVTMxEi7sBEK6XUq3QwVgbY3Erv0u79GQVqjsUww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Oct 29, 2020 at 5:13 PM Bryn Llewellyn <bryn(at)yugabyte(dot)com> wrote:
> «
> Selects the data format to be read or written: text, csv (Comma Separated
> Values), or binary. The default is text.
> »
>
> would be improved if it were spelled more explicitly:
>
> «
> Selects the data format to be read or written. The allowed values
> for format_name are text, csv (Comma Separated Values), or binary. The
> default is text.
> »
>
> Please consider making this change (and the convention that it implies for
> comparable cases).
>
While I agree it isn't something I'm going to lead the charge on. As you
are expressing strong feelings maybe you'd like to write up a patch.
Fixing only COPY would suffice even though I suspect that there are other
areas that need consideration.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jürgen Purtz | 2020-10-30 10:57:04 | Re: Additional Chapter for Tutorial |
Previous Message | Bryn Llewellyn | 2020-10-30 00:13:22 | Re: COPY statement: no list of the allowed values for "format_name" |