| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "Leonardo M(dot) Ramé" *EXTERN* <martinrame(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Weird encoding behavior |
| Date: | 2009-03-26 15:34:52 |
| Message-ID: | 22330.1238081692@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> 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 "NUEZ".
> 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...
Yeah, I think this destroys the theory that it's due to a wrong choice
of client_encoding setting. What you'd be likely to get from that is
a "character can't be translated" kind of error, not silent substitution
of a question mark. The damage must be getting done on the client side.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alan Hodgson | 2009-03-26 15:43:53 | Re: Question about hosting and server grade |
| Previous Message | Sam Mason | 2009-03-26 15:32:46 | Re: HINT: Please REINDEX it? |