From 41a40fe4a2acc1256556754228a650610dbffa42 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 17 Sep 2009 21:13:01 +0000 Subject: [PATCH] CVS NULL Documentation Clearify documentation of CVS's output of NULL values, per suggestion from Magnus. Backpatch to 8.4.X. --- doc/src/sgml/ref/copy.sgml | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 8ab9ff7eca..ff91ee2d9f 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -1,5 +1,5 @@ @@ -550,13 +550,10 @@ COPY count 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 + PostgreSQL's COPY handles this using + quoting. A NULL is output as an empty string without + quotes, while an empty string data value is double-quoted + (""). Reading values follows similar rules. You can use FORCE NOT NULL to prevent NULL input comparisons for specific columns.