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

Поиск
Список
Период
Сортировка
От Marius Žalinauskas
Тема Re: BUG #2535: Unicode on Windows: aogonek is not distinguished from agrave
Дата
Msg-id 000101c6ab69$45f41e20$0a54a8c0@aleja.local
обсуждение исходный текст
Ответ на BUG #2535: Unicode on Windows: aogonek is not distinguished from agrave  ("Marius Žalinauskas" <mariusz@splius.lt>)
Список 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@splius.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 ('À');




В списке pgsql-bugs по дате отправления:

Предыдущее
От: Thiago Silva
Дата:
Сообщение: XML2 module: odd query results
Следующее
От: "David Fetter"
Дата:
Сообщение: BUG #2539: PL/PgSQL doesn't disallow COPY commands on compile, even though it disallows them.