On 09/05/2013 10:02 AM, Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>> 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.
There's certainly alternatives. But all of the alternatives increase
the cost of the migration (either in staff time or in downtime), which
increases the likelyhood that the organization will abandon the migration.
Anyway, I think we've established that there are enough "legitimate"
uses for SQL_ASCII that we can't casually discard it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com