If you use Latin2 encoding, you can not have 'bssz' and 'bszsz' in an
unique column in the same time.
Is this a known bug? Do you have any solution? (I use Latin2 encoding,
because I want to order by names, which contains accent characters.)
d43m0n(at)jerry:~> psql template1
Welcome to psql 7.4.2, the PostgreSQL interactive terminal.
template1=# CREATE DATABASE test WITH ENCODING = 'LATIN2';
template1=# \c test
You are now connected to database "test".
test=# CREATE TABLE test (name character varying (128) UNIQUE NOT NULL);
NOTICE: CREATE TABLE / UNIQUE will create implicit index
"test_name_key" for table "test"
test=# INSERT INTO test (name) VALUES ('bssz');
INSERT 17798 1
test=# INSERT INTO test (name) VALUES ('bszsz');
ERROR: duplicate key violates unique constraint "test_name_key"
I am running Debian Sid i386 with 2.6.6 kernel, libc6 2.3.2.ds1-12,
locales 2.3.2.ds1-12, postgresql 7.4.2-4 . Locale for postgres user is
"POSIX", locale for the psql client is "hu_HU". Both client and server
encoding for the above connections was Latin2.
PS: Please CC me, I am not subscribed to the list.
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2004-05-20 16:41:41|
|Subject: Re: int4, int8, real ....division... |
|Previous:||From: Bruce Momjian||Date: 2004-05-20 01:40:05|
|Subject: Re: BUG #1144: comments don't get propagated|