Can I see an example of such a failure line?

---------------------------------------------------------------------------

Andrew Dunstan wrote:
> 
> Darcy Buskermolen has drawn my attention to unfortunate behaviour of 
> COPY CSV with fields containing embedded line end chars if the embedded 
> sequence isn't the same as those of the file containing the CSV data. In 
> that case we error out when reading the data in. This means there are 
> cases where we can produce a CSV data file which we can't read in, which 
> is not at all pleasant.
> 
> Possible approaches to the problem:
> . make it a documented limitation
> . have a "csv read" mode for backend/commands/copy.c:CopyReadLine() that 
> relaxes some of the restrictions on inconsistent line endings
> . escape embedded line end chars
> 
> The last really isn't an option, because the whole point of CSVs is to 
> play with other programs, and my understanding is that those that 
> understand multiline fields (e.g. Excel) expect them not to be escaped, 
> and do not produce them escaped.
> 
> So right now I'm tossing up in my head between the first two options. Or 
> maybe there's another solution I haven't thought of.
> 
> Thoughts?
> 
> cheers
> 
> andrew
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org

Reply via email to