From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Fwd: Copy out wording |
Date: | 2009-09-03 07:52:45 |
Message-ID: | 9837222c0909030052j546aaf4bs6348aed3d08f927f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-hackers |
Crap, I just realized I sent to pgadmin hackers by mystake. Meh.
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/
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2009-09-03 11:12:30 | Re: [pgAdmin III] #47: Savepoints in PgAdmin |
Previous Message | Dave Page | 2009-09-03 07:37:22 | Re: pgAdmin and Slony |
From | Date | Subject | |
---|---|---|---|
Next Message | Ľubomír Varga | 2009-09-03 08:35:11 | suggestion to improve planer |
Previous Message | Itagaki Takahiro | 2009-09-03 07:25:10 | Re: Triggers on columns |