database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-09 18:21:05 +03:00
Code

Remove documentation that CSV didn't handle carriage returns and line

Browse Source 
feeds properly.
This commit is contained in:
Bruce Momjian 2005-05-06 03:38:05 +00:00
parent 902338e06d
commit 051ecca022
1 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/ref/copy.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.63 2005/01/04 00:39:53 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.64 2005/05/06 03:38:05 momjian Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -497,12 +497,7 @@ COPY <replaceable class="parameter">tablename</replaceable> [ ( <replaceable cla
CSV mode will both recognize and produce CSV files with quoted CSV mode will both recognize and produce CSV files with quoted
values containing embedded carriage returns and line feeds. Thus values containing embedded carriage returns and line feeds. Thus
the files are not strictly one line per table row like text-mode the files are not strictly one line per table row like text-mode
files. However, <productname>PostgreSQL</productname> will reject files.
<command>COPY</command> input if any fields contain embedded line
end character sequences that do not match the line ending
convention used in the CSV file itself. It is generally safer to
import data containing embedded line end characters using the
text or binary formats rather than CSV.
</para> </para>
</note> </note>