Re: BUG #2535: Unicode on Windows: aogonek is not distinguished from agrave

From: Marius Žalinauskas <mariusz(at)splius(dot)lt>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #2535: Unicode on Windows: aogonek is not distinguished from agrave
Date: 2006-07-19 19:26:45
Message-ID: 000101c6ab69$45f41e20$0a54a8c0@aleja.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

For the record: the original BUG #2535 report should be viewed in UTF-8 to see inserted values.

--
Marius Zalinauskas

> The following bug has been logged online:
>
> Bug reference: 2535
> Logged by: Marius Žalinauskas
> Email address: mariusz(at)splius(dot)lt
> PostgreSQL version: 8.1.4
> Operating system: Windows XP Pro
> Description: Unicode on Windows: aogonek is not
> distinguished from
> agrave
> Details:
>
> It seems that on Windows PostgreSQL v8.1.4 does not
> distinguish aogonek
> (U+0104, U+0105) from agrave (U+00C0, U+00E0):
>
> CREATE DATABASE tests ENCODING = 'UTF8';
>
> \c tests
>
> CREATE TABLE foo
> (
> bar char(1) PRIMARY KEY
> );
>
> -- OK
> INSERT INTO foo (bar) VALUES ('ą');
>
> -- ERROR: duplicate key violates unique constraint
> INSERT INTO foo (bar) VALUES ('à');
>
> -- Same thing with capitals
>
> -- OK
> INSERT INTO foo (bar) VALUES ('Ą');
>
> -- ERROR: duplicate key violates unique constraint
> INSERT INTO foo (bar) VALUES ('À');

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Fetter 2006-07-19 22:46:17 BUG #2539: PL/PgSQL doesn't disallow COPY commands on compile, even though it disallows them.
Previous Message Tom Lane 2006-07-19 19:22:01 Re: double insert on inherited table with where constraint based on sequence