Skip site navigation (1) Skip section navigation (2)

Re: BUG #3323: Wrong charset for the lower and upper functions

From: "Eduardo Ferreira" <eduardo(dot)edusantos(at)gmail(dot)com>
To: "Euler Taveira de Oliveira" <euler(at)timbira(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3323: Wrong charset for the lower and upper functions
Date: 2007-05-31 03:10:31
Message-ID: 266b12630705302010i21e4a870n250d0d47013e0d1d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi,

I haven't seen this issue for windows console, but I don't think it affects
my DB. Anyway, I'm using Unicode (UTF8), and this is the only problem I had.
If it had something to do with the encoding, the results would be very
different (such as the wrong character as result for the function).

My guess is that the order is reversed for the ç only. I'll try to fix the
windows console issue and tell you the results later. Thanks for your help.

2007/5/30, Euler Taveira de Oliveira <euler(at)timbira(dot)com>:
>
> Eduardo Santos wrote:
>
> > When you have the latin character ç and use the lower or the upper
> > function, instead of return the approprite character, it returns the
> oposite
> > one, so the comparisons in the whole DB are wrong. If you have a word
> such
> > as Serviço, and you use the lower function, the result is serviÇo,
> instead
> > of serviço. the other side is also true: if you use upper in the same
> eord,
> > the result is SERVIçO, instead of SERVIÇO.
> >
> Did you read [1] for issues with code page on Windows console windows?
> What kind of encoding are you using? I haven't reproduce your problem
> here.
>
> [1] http://www.postgresql.org/docs/8.2/static/app-psql.html
>
> --
>   Euler Taveira de Oliveira
>   http://www.timbira.com/
>

In response to

pgsql-bugs by date

Next:From: Galy LeeDate: 2007-05-31 09:14:06
Subject: BUG #3326: Invalid lower bound of autovacuum_cost_limit
Previous:From: Euler Taveira de OliveiraDate: 2007-05-31 02:55:15
Subject: Re: BUG #3323: Wrong charset for the lower and upper functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group