| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> | 
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: COPY formatting | 
| Date: | 2004-03-18 22:42:59 | 
| Message-ID: | 405A25F3.50108@dunslane.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Joshua D. Drake wrote:
>>
>> 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
*nod* I too have seen these and other variants over the years, including 
some that use single quote instead of double quote as the quote char, 
and \ as the escape char.
My suggested scheme for beefing up COPY was made with all these variants 
in mind.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-03-18 22:55:20 | Re: Further thoughts about warning for costly FK checks | 
| Previous Message | Jonathan Gardner | 2004-03-18 22:37:27 | Bug in CVS HEAD on bootparse.y??? |