Re: Best practices for moving UTF8 databases

> "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