"Albe Laurenz" writes:
> Leonardo M. Ramé wrote:
>> 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 *befor
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
"Leonardo M. Ramé" wrote:
> Hi, I'm experiencing a weird behavior when storing latin characters to a
> PostgreSQL 8.3.1.876 server. The database is Latin1 encoded, and it is
> working since September 2008, it wasn't updated nor replaced since its
> first installation.
>
> The weirdness of the
Well, there *must* be one client that stores wrong data...
You are right, I'll ask someone in site to look at *each* client hunting
for the root of the problem. It must be a Windows Regional Settings or
something similar.
As a first step, can you find out the code point of the character th
Leonardo M. Ramé wrote:
> Hi, I'm experiencing a weird behavior when storing latin characters to a
> PostgreSQL 8.3.1.876 server. The database is Latin1 encoded, and it is
> working since September 2008, it wasn't updated nor replaced since its
> first installation.
>
> The weirdness of the pro
Hola
use Ñ for spanish N
http://webdesign.about.com/od/localization/l/blhtmlcodes-sp.htm
Saludos Cordiales desde EEUU!
Martin
__
Disclaimer and confidentiality note
This message is confidential and may be privileged. If you are not the intended
rec
