Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 41a40fe

Browse files
committed
CVS NULL Documentation
Clearify documentation of CVS's output of NULL values, per suggestion from Magnus. Backpatch to 8.4.X.
1 parent 44608ae commit 41a40fe

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

doc/src/sgml/ref/copy.sgml

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.87 2009/09/05 23:58:01 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.88 2009/09/17 21:13:01 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -550,13 +550,10 @@ COPY <replaceable class="parameter">count</replaceable>
550550
<para>
551551
The <literal>CSV</> format has no standard way to distinguish a
552552
<literal>NULL</> value from an empty string.
553-
<productname>PostgreSQL</>'s <command>COPY</> handles this by
554-
quoting. A <literal>NULL</> is output as the <literal>NULL</>
555-
string and is not quoted, while a data value matching the
556-
<literal>NULL</> string is quoted. Therefore, using the default
557-
settings, a <literal>NULL</> is written as an unquoted empty
558-
string, while an empty string is written with double quotes
559-
(<literal>""</>). Reading values follows similar rules. You can
553+
<productname>PostgreSQL</>'s <command>COPY</> handles this using
554+
quoting. A <literal>NULL</> is output as an empty string without
555+
quotes, while an empty string data value is double-quoted
556+
(<literal>""</>). Reading values follows similar rules. You can
560557
use <literal>FORCE NOT NULL</> to prevent <literal>NULL</> input
561558
comparisons for specific columns.
562559
</para>

0 commit comments

Comments
 (0)