Re: Underscorces in copy-documentation (9.0 and higher)

From: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mario Duhanic <duhanic(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Underscorces in copy-documentation (9.0 and higher)
Date: 2013-03-20 14:49:10
Message-ID: CAB8KJ=ia8nT=6K3XN19o9BOBoLYGLNZTbwCC39ZnuOBjs=p-WA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

2013/3/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Mario Duhanic <duhanic(at)gmail(dot)com> writes:
>> Hi,
>> - http://www.postgresql.org/docs/9.2/static/sql-copy.html,
>> - http://www.postgresql.org/docs/9.1/static/sql-copy.html and
>> - http://www.postgresql.org/docs/9.0/static/sql-copy.html
>
>> have underscores ("_") where there should be none,
>> e.g. in "FORCE_QUOTES".
>
> Huh? The references to FORCE_QUOTE look correct to me. The syntax
> doesn't support multi-word option names, so it has to be like that
> (or else run the words together, which doesn't sound like an
> improvement).

FWIW, multi-word option names are pre-9.0 syntax and still supported.
This is documented, albeit you have to scroll to the bottom of the page:

http://www.postgresql.org/docs/current/static/sql-copy.html#AEN66823

Regards

Ian Barwick

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Mario Duhanic 2013-03-20 14:50:05 Fwd: Underscorces in copy-documentation (9.0 and higher)
Previous Message Tom Lane 2013-03-20 14:05:49 Re: Underscorces in copy-documentation (9.0 and higher)