Re: Best practices for moving UTF8 databases - Mailing list pgsql-general

From Phoenix Kiula
Subject Re: Best practices for moving UTF8 databases
Date
Msg-id e373d31e0907201843x5714b99fh161d60c3dc9b651e@mail.gmail.com
Whole thread Raw
In response to Re: Best practices for moving UTF8 databases  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: Best practices for moving UTF8 databases
Re: Best practices for moving UTF8 databases
List 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

pgsql-general by date:

Previous
From: Phoenix Kiula
Date:
Subject: Re: First query very slow. Solutions: memory, or settings, or SQL?
Next
From: Dennis Gearon
Date:
Subject: commercial adaptation of postgres