Re: pgsql: doc: improve wording of COPY commit 7ec73783d88a743799b0c262f12

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: doc: improve wording of COPY commit 7ec73783d88a743799b0c262f12
Date: 2014-04-23 00:33:04
Message-ID: 20140423003304.GN10046@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Apr 22, 2014 at 07:55:56PM -0400, Andrew Dunstan wrote:
>
>
>
>
> On 04/22/2014 07:16 PM, Bruce Momjian wrote:
> >doc: improve wording of COPY commit 7ec73783d88a743799b0c262f1235f772497fb1d
> >
>
>
> This isn't an improvement: it's made it incorrect. The null string
> is not necessarily empty, it is only empty by default. People keep
> making this mistake (and indeed, the original patch made the same
> mistake in its code, which I corrected), probably because specifyng
> anything other than the empty string is unusual. However, snice we
> have made provision for it not to be empty we should describe it
> accurately.

Sorry, fixed. Thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2014-04-23 00:33:19 pgsql: doc: adjust 9970443640b4569cf72b3c8e84abe80bdf533c7f for "null
Previous Message Andrew Dunstan 2014-04-22 23:55:56 Re: pgsql: doc: improve wording of COPY commit 7ec73783d88a743799b0c262f12