Re: How to insert Ecoded values into postrgresql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, venkat <ven(dot)tammineni(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: How to insert Ecoded values into postrgresql
Date: 2010-04-19 17:06:37
Message-ID: 17204.1271696797@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> *) csv is supposed to be CRLF *always*. We do not do this. We do
> however read different types of newlines. So we are a 4180 reader but
> not an emitter. Not so sure if I think changing this is a good idea
> though without exposing a knob.

Given the lack of field complaints, I think changing this would be a
pretty terrible idea; much more likely to break things than fix them.
It's not like that RFC has huge recognition as The Standard.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2010-04-19 17:07:40 Re: Virtual table with pl/perl?
Previous Message Scott Marlowe 2010-04-19 17:06:18 Re: performance problems inserting random vals in index