Re: [BUGS] uniqueness not always correct
От | Vadim Mikheev |
---|---|
Тема | Re: [BUGS] uniqueness not always correct |
Дата | |
Msg-id | 382A955D.56098552@krs.ru обсуждение исходный текст |
Ответы |
Re: [HACKERS] Re: [BUGS] uniqueness not always correct
Re: [BUGS] uniqueness not always correct Re: [BUGS] uniqueness not always correct Re: [BUGS] uniqueness not always correct Re: [BUGS] uniqueness not always correct |
Список | pgsql-hackers |
Frank Cusack wrote: > > Solaris 2.6/sparc; postgres 6.5.1 > > dns=> create table test (zone int4, net cidr, unique(zone, net)); > NOTICE: CREATE TABLE/UNIQUE will create implicit index 'test_zone_key' for table 'test' > CREATE > dns=> insert into test (zone, net) values (1, '1.2.3/24'); > INSERT 21750 1 > dns=> insert into test (zone, net) values (1, '2.3.4/24'); > INSERT 21751 1 > dns=> insert into test (zone, net) values (1, '1.2.3/24'); > INSERT 21752 1 > dns=> insert into test (zone, net) values (1, '2.3.4/24'); > ERROR: Cannot insert a duplicate key into a unique index Yes, I reproduced this (Solaris 2.5/sparc). Seems like CIDR problem(??!): ais=> create table test (zone int4, net int4, unique(zone, net)); ^^^^ NOTICE: CREATE TABLE/UNIQUE will create implicit index 'test_zone_key' for table 'test' CREATE ais=> insert into test (zone, net) values (1, 1); INSERT 7712479 1 ais=> insert into test (zone, net) values (1, 2); INSERT 7712480 1 ais=> insert into test (zone, net) values (1, 1); ERROR: Cannot insert a duplicate key into a unique index Vadim
В списке pgsql-hackers по дате отправления: