| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: \COPY ... CSV with hex escapes |
| Date: | 2010-07-08 09:42:51 |
| Message-ID: | 03259A04-207C-4627-8C8A-A10AE174B34E@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8 Jul 2010, at 4:21, Craig Ringer wrote:
> Yes, that's ancient. It is handled quite happily by \copy in csv mode,
> except that when csv mode is active, \xnn escapes do not seem to be
> processed. So I can have *either* \xnn escape processing *or* csv-style
> input processing.
>
> Anyone know of a way to get escape processing in csv mode?
And what do those hex-escaped bytes mean? Are they in text strings? AFAIK CSV doesn't contain any information about what encoding was used to create it, so it could be about anything; UTF-8, Win1252, ISO-8859-something, or whatever Sybase was using.
I'm just saying, be careful what you're parsing there ;)
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c359d9f286212106016419!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2010-07-08 10:47:32 | CREATE PROCEDURAL LANGUAGE plpythonu on windows, with EDB's 8.4.2 installer causes error |
| Previous Message | Dave Page | 2010-07-08 07:53:22 | Re: Problems with Vista and Windows 7 |