Bug #823: upper() does not handle �, � and � correctly.

Started by PostgreSQL Bugs Listover 23 years ago3 messagesbugs
Jump to latest
#1PostgreSQL Bugs List
pgsql-bugs@postgresql.org

Marcus Andersson (maran@fyrplus.se) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
upper() does not handle �, � and � correctly.

Long Description
The function upper() just leaves the letters �, �, and � unmodified. It should replace them with �, � and � respectively.

PostgreSQL version 7.2.3 on Solaris.

I am using encoding 7 (ISO 8859-1).

Sample Code

No file was uploaded with this report

#2Stephan Szabo
sszabo@megazone23.bigpanda.com
In reply to: PostgreSQL Bugs List (#1)
Re: [BUGS] Bug #823: upper() does not handle �, � and � correctly.

On Tue, 26 Nov 2002 pgsql-bugs@postgresql.org wrote:

Marcus Andersson (maran@fyrplus.se) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
upper() does not handle �, � and � correctly.

Long Description
The function upper() just leaves the letters �, �, and � unmodified.
It should replace them with �, � and � respectively.

PostgreSQL version 7.2.3 on Solaris.

I am using encoding 7 (ISO 8859-1).

It's probably a locale issue. What locale did you initdb in?

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: PostgreSQL Bugs List (#1)
Re: Bug #823: upper() does not handle , and correctly.

pgsql-bugs@postgresql.org writes:

upper() does not handle �, � and � correctly.

Sounds like you didn't set your locale correctly --- this is not an
encoding issue, it is a locale issue.

regards, tom lane