Re: Weird encoding behavior - Mailing list pgsql-general

From Albe Laurenz
Subject Re: Weird encoding behavior
Date
Msg-id D960CB61B694CF459DCFB4B0128514C202FF6511@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Re: Weird encoding behavior  ("Leonardo M. Ramé" <martinrame@yahoo.com>)
Responses Re: Weird encoding behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Leonardo M. Ramé wrote:
> > As a first step, can you find out the code point of the character that
> > is represented as "?" in your E-Mail?
> >
> > Something like
> > SELECT ascii(substr('NU?EZ', 3, 1));
> > except that instead of the string literal you substitute the column
> > containing the bad value.
>
> I did what you suggested, and it responds with a 63 when the string is
> "NU?NEZ" and 209 when it's "NUÑEZ".

63 is indeed a question mark. Since such a conversion would not be
done by PostgreSQL, "something else" must convert Ñ to ?N *before*
it gets into PostgreSQL...

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: "Marc Mamin"
Date:
Subject: ltree and full text search questions
Next
From: Sam Mason
Date:
Subject: Re: Question about hosting and server grade