|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.87 2009/09/05 23:58:01tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.88 2009/09/17 21:13:01momjian Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -550,13 +550,10 @@ COPY <replaceable class="parameter">count</replaceable> |
550 | 550 | <para> |
551 | 551 | The <literal>CSV</> format has no standard way to distinguish a |
552 | 552 | <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 |
560 | 557 | use <literal>FORCE NOT NULL</> to prevent <literal>NULL</> input |
561 | 558 | comparisons for specific columns. |
562 | 559 | </para> |
|