Yes, I can confirm this is now fixed.
> 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=> in
I can confirm this is fixed in the current source tree, to be released
as 7.1 in a few months:
test=> 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
test=> insert into test (zone, net) va
Tom Lane writes:
[CIDR and INET]
> Alternatively, if no one cares enough about these types to even
> understand what they should do, maybe we should rip 'em out?
Actually, I'm a happy user of these types, so that would certainly make me
unhappy...
CIDR stores network addresses, so '10.8/16' mig
Bruce Momjian <[EMAIL PROTECTED]> writes:
> This bug appears to still exist in 7.0:
> test=> create table test (zone int4, net cidr, unique(zone, net));
Yeah. IIRC, the issue is that the CIDR data-type-specific btree
comparison function looks at all bits in the datatype, including bits
tha
This is Vadim's comment on the bug.
> 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=> inse
This bug appears to still exist in 7.0:
test=> 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
test=> insert into test (zone, net) values (1,
