Skip site navigation (1) Skip section navigation (2)

Re: multiline CSV fields

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multiline CSV fields
Date: 2004-11-29 14:23:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches

Bruce Momjian wrote:

>Also, can you explain why we can't read across a newline to the next
>quote?  Is it a problem with the way our code is structured or is it a
>logical problem?  Someone mentioned multibyte encodings but I don't
>understand how that applies here.

In a CSV file, each line is a record. Reading across a newline for the 
next quote (assuming the next field is quoted) would mean stealing 
fields from the next record.

I did see one complaint about missing or extra fields at the end of a 
record - I think it is reasonable for us to expect the data to be 
rectangular, and not ragged.

(I hope this answers your question - I am not 100% certain I understaood 



In response to

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2004-11-29 14:48:40
Subject: Re: Error: column "nsptablespace" does not exist
Previous:From: Simon RiggsDate: 2004-11-29 14:01:00
Subject: Re: Documentation on PITR still scarce

pgsql-patches by date

Next:From: Tom LaneDate: 2004-11-29 15:42:29
Subject: Re: multiline CSV fields
Previous:From: Andrew DunstanDate: 2004-11-29 14:00:28
Subject: Re: multiline CSV fields

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group