Re: Best practices for moving UTF8 databases

From: Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best practices for moving UTF8 databases
Date: 2009-07-21 01:43:55
Message-ID: e373d31e0907201843x5714b99fh161d60c3dc9b651e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> "0x80" makes me think of the following:
> The data originate from a Windows system, where 0x80 is a Euro
> sign. Somehow these were imported into PostgreSQL without the
> appropriate translation into UTF-8 (how I do not know).
>
> I wonder: why do you spend so much time complaining instead of
> simply locating the buggy data and fixing them?

I'd love to fix them. But if I do a search for

SELECT * FROM xyz WHERE col like '%0x80%'

it doesn't work. How should I search for these characters?

Thanks much

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dennis Gearon 2009-07-21 01:56:39 commercial adaptation of postgres
Previous Message Phoenix Kiula 2009-07-21 01:36:41 Re: First query very slow. Solutions: memory, or settings, or SQL?