Re: COPY formatting

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: josh(at)agliodbs(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY formatting
Date: 2004-03-18 22:28:06
Message-ID: 405A2276.4090105@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> And, BTW, I deal with CSV *all the time* for my insurance clients, and I can
> tell you that that format hasn't changed in 20 years. We can hard-code it
> if it's easier.

Well many of my clients consider CSV "Character Separated Value" not
Comma... Thus I get data like this:

"Hello","Good Bye"
Hello Good Bye
Hello,Good Bye
"This", "They're"
This They're
"This" "Is" "A" 1

Dealing with all of these different nuances is may or may not be beyond
the scope of copy but it seems that it could be something that it can
handle.

Python has a csv module that allows you to assign dialects to any
specific type of import you are performing.

Sincerely,

Joshua D. Drake

>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

Attachment Content-Type Size
jd.vcf text/x-vcard 640 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan Gardner 2004-03-18 22:37:27 Bug in CVS HEAD on bootparse.y???
Previous Message Josh Berkus 2004-03-18 21:39:07 Authentication drop-down?