Re: multiline CSV fields

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multiline CSV fields
Date: 2004-11-29 15:42:29
Message-ID: 18519.1101742949@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> 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?

It's a structural issue in the sense that we separate the act of
dividing the input into rows from the act of dividing it into columns.
I do not think that separation is wrong however.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2004-11-29 15:43:35 set variable for TOAST_TUPLE_THRESHOLD
Previous Message Tom Lane 2004-11-29 15:37:32 Re: Stopgap solution for table-size-estimate updatingproblem

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-11-29 16:59:28 Re: BUG #1329: Bug in IF-ELSEIF-ELSE construct
Previous Message Andrew Dunstan 2004-11-29 14:23:57 Re: multiline CSV fields