From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-15 13:53:37 |
Message-ID: | y2mb42b73151004150653n5199a7a2m49e2feb42961842b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 15, 2010 at 12:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> Merlin Moncure wrote:
>>> aside: anyone know if postgres properly handles csv according to rfc4180?
>
>> Wow, I had no idea there was an RFC for CSV.
>
> Me either. I'd bet the percentage of "CSV"-using programs that actually
> conform to the RFC is very small anyway; so while it might be smart to
> make sure that what we *emit* follows the RFC, it's probably useless as
> a guide to what we need to *accept*.
Well, we would have to accept it if we emit it, but you're right.
Kinda like how with base64 encoding there are two competing
incompatible (both RFC) standards of doing it. We accept both but
only emit one. I'll look at how we handle csv. I've always been
curious about that actually. If a standard exists and it isn't
completely insane maybe we should document and encourage it.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Krcmar | 2010-04-15 13:56:20 | Re: VACUUM process running for a long time |
Previous Message | Satish Burnwal (sburnwal) | 2010-04-15 13:31:41 | Re: Query is stuck |