From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: get rid of SQL_ASCII? |
Date: | 2013-09-05 17:02:17 |
Message-ID: | 20130905170216.GC6067@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua D. Drake wrote:
>
> On 09/05/2013 09:42 AM, Josh Berkus wrote:
> >>Other ideas? Are there legitimate uses for SQL_ASCII?
> >
> >Migrating from MySQL. We've had some projects where we couldn't fix
> >MySQL's non-enforcement text garbage, and had to use SQL_ASCII on the
> >receiving side. If it hadn't been available, the user would have given
> >up on Postgres.
>
> iconv?
Command Prompt helped a customer normalize encodings in their data,
which was a mixture of Latin1 and UTF8. PGLoader was used for this, in
two stages; the first run in UTF8 saved the rejected data to a file
which was loaded in the second run as Latin1. This worked like a charm.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-09-05 17:02:47 | Re: improve Chinese locale performance |
Previous Message | Andres Freund | 2013-09-05 16:59:44 | Re: lcr v5 - introduction of InvalidCommandId |