MIME-Version: 1.0
In-Reply-To: <1553.1363788349@sss.pgh.pa.us>
References: 
 <CAFOaSD1XwZM+cJOmphMDzNCzPJBYszv_ELD4ZaPkk0u9d0bMhg@mail.gmail.com>
	<1553.1363788349@sss.pgh.pa.us>
Date: Wed, 20 Mar 2013 23:49:10 +0900
Message-ID: 
 <CAB8KJ=ia8nT=6K3XN19o9BOBoLYGLNZTbwCC39ZnuOBjs=p-WA@mail.gmail.com>
Subject: Re: Underscorces in copy-documentation (9.0 and higher)
From: Ian Lawrence Barwick <barwick@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mario Duhanic <duhanic@gmail.com>, pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

2013/3/20 Tom Lane <tgl@sss.pgh.pa.us>:
> Mario Duhanic <duhanic@gmail.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


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs