| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY formatting |
| Date: | 2004-03-22 06:46:23 |
| Message-ID: | 20040322064623.GA9385@zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 19, 2004 at 09:54:37AM -0500, Tom Lane wrote:
> Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
> > The problem with CSV is that it will correctly work with new protocol
> > only. Because old versions of clients are newline sensitive.
>
> Why? The client-side code doesn't have any real say over the meaning of
> the data, at least not in psql-class clients. I suppose a client app
> that tries to interpret the data could get confused, but psql sure
> doesn't do that.
libpq, fe-protocol2.c, pqGetCopyData2() and pqGetline2() cut string
behind '\n'.
Karel
--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2004-03-22 07:35:37 | Re: pg_autovacuum next steps |
| Previous Message | Manfred Spraul | 2004-03-22 06:12:59 | Re: [HACKERS] libpq thread safety |