Copy out wording

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Copy out wording
Date: 2009-09-01 12:51:07
Message-ID: 9837222c0909010551lfa4a4f5j736cabc8d9c540ff@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgsql-hackers

Our documentation for COPY
(http://www.postgresql.org/docs/8.4/static/sql-copy.html) has the
following to say:
"
The CSV format has no standard way to distinguish a NULL value from
an empty string. PostgreSQL's COPY handles this by quoting. A NULL is
output as the NULL string and is not quoted, while a data value
matching the NULL string is quoted. Therefore, using the default
settings, a NULL is written as an unquoted empty string, while an
empty string is written with double quotes (""). Reading values
follows similar rules. You can use FORCE NOT NULL to prevent NULL
input comparisons for specific columns.
"

Shouldn't that be:
"A NULL is output as the NULL string and is not quoted, while a data
value matching the empty string is quoted"?

If not, then what really is the difference between a NULL and a NULL string?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message svn 2009-09-02 17:42:58 SVN Commit by guillaume: r8027 - branches/REL-1_10_0_PATCHES/pgadmin3/i18n/sr_RS
Previous Message pgAdmin Trac 2009-09-01 12:36:03 Re: [pgAdmin III] #50: Domain wizard bug

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-09-01 13:49:04 Re: [COMMITTERS] pgsql: Move processing of startup-packet switches and GUC settings into
Previous Message Werner Echezuria 2009-09-01 12:39:57 Re: Bison crashes postgresql