| From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgman(at)candle(dot)pha(dot)pa(dot)us, chriskl(at)familyhealth(dot)com(dot)au, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Different length lines in COPY CSV |
| Date: | 2005-12-12 20:30:12 |
| Message-ID: | 1134419412.4975.86.camel@Andrea.peacock.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Montag, den 12.12.2005, 15:08 -0500 schrieb Andrew Dunstan:
>
> Tom Lane wrote:
...
>
> You are probably right. The biggest wrinkle will be dealing with various
> encodings, I suspect. That at least is one thing that doing CSV within
> the backend bought us fairly painlessly. Perl's Text::CSV_XS module for
> example simply handles this by declaring that only [\x09\x20-\x7f] are
> valid in its non-binary mode, and in either mode appears to be MBCS
> unaware. We should try to do better than that.
Are there any test datafiles available in a repository?
I could give it a shot I think.
If not maybe we could set up something like that.
Regards
Tino
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-12-12 20:35:45 | Re: Different length lines in COPY CSV |
| Previous Message | Francisco Figueiredo Jr. | 2005-12-12 20:26:25 | [Bug] Server Crash, possible security exploit, where to send security report? |