Re: BUG #1557: UPPER() and LOWER() do not return the right characters

Try the replacement upper/lower functions that I wrote:

http://archives.postgresql.org/pgsql-hackers/2005-02/msg00102.php=20

Kind regards,

John Hansen

> -----Original Message-----
> From: pgsql-bugs-owner@postgresql.org=20
> [mailto:pgsql-bugs-owner@postgresql.org] On Behalf Of Staffan Sandberg
> Sent: Tuesday, March 22, 2005 8:28 PM
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] BUG #1557: UPPER() and LOWER() do not return=20
> the right characters
>=20
>=20
> The following bug has been logged online:
>=20
> Bug reference:      1557
> Logged by:          Staffan Sandberg
> Email address:      staffan.sandberg@fhd.se
> PostgreSQL version: 7.4.6-1.FC2.2
> Operating system:   Fedora Core 2
> Description:        UPPER() and LOWER() do not return the=20
> right characters
> Details:=20
>=20
> Hi,
>=20
> I am using a PostgreSQL DB with the LATIN1 (ISO-8859-1)=20
> character encoding.
> When using the UPPER() or LOWER() functions on any of our=20
> swedish specific characters the returned character is never=20
> transformed to the desired case.
> The functions only return the same character as the input,=20
> disregarding of the input character's case.
>=20
> E.g: LOWER('=C3-') should return '=C3=B6' but instead '=C3-' is returned.
>=20
> The concerned characters are:
> LOWER     UPPER
> =C3=A5         =C3...
> =C3=A4         =C3"
> =C3=B6         =C3-
>=20
> To solve the problem I am now forced to use the REPLACE()=20
> function for these three characters, hence it would be more=20
> convinient if the LOWER() and
> UPPER() functions worked properly.
>=20
> Please make a comment on my report!
> Kind regards,
> Staffan Sandberg
>=20
> ---------------------------(end of=20
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>=20
>=20