Re: multiline CSV fields

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Patrick B Kelly <pbk(at)patrickbkelly(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multiline CSV fields
Date: 2004-11-11 23:16:49
Message-ID: 12778.1100215009@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Patrick B Kelly <pbk(at)patrickbkelly(dot)org> writes:
> What about just coding a FSM into
> backend/commands/copy.c:CopyReadLine() that does not process any flavor
> of NL characters when it is inside of a data field?

CopyReadLine has no business tracking that. One reason why not is that
it is dealing with data not yet converted out of the client's encoding,
which makes matching to user-specified quote/escape characters
difficult.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew McMillan 2004-11-11 23:20:24 Re: A modest proposal: get rid of GUC's USERLIMIT
Previous Message Andrew Dunstan 2004-11-11 23:15:15 Re: multiline CSV fields

Browse pgsql-patches by date

  From Date Subject
Next Message Patrick B Kelly 2004-11-12 02:40:09 Re: multiline CSV fields
Previous Message Andrew Dunstan 2004-11-11 23:15:15 Re: multiline CSV fields