Re: How to insert Ecoded values into postrgresql

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, 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-20 14:55:29
Message-ID: 201004201455.o3KEtT915911@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> 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.

Should we document we support the standard?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-04-20 15:07:54 Re: How to insert Ecoded values into postrgresql
Previous Message Ozz Nixon 2010-04-20 14:52:56 Anyone use Python/ceODBC/PostgreSQL?