Re: Unique and Primary Key Constraints - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Unique and Primary Key Constraints
Date
Msg-id 1026572902.30427.161.camel@jester
Whole thread Raw
In response to Re: Unique and Primary Key Constraints  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Unique and Primary Key Constraints
Re: Unique and Primary Key Constraints
List pgsql-hackers
On Sat, 2002-07-13 at 10:29, Bruce Momjian wrote:
> Rod Taylor wrote:
> > > > I prefer ...add constraint.  After a while (release or 2) removal of
> > > > create unique index all together.
> > > 
> > > Remove CREATE UNIQUE INDEX entirely?  Why?
> > 
> > I was looking to encourage users to use core SQL as I spend more time
> > than I want converting between systems -- thanks in part to users who
> > create non-portable structures.
> > 
> > Temporarily forgot there are index types other than btree :)
> 
> Not so much non-btree, but non-unique indexes themselves.  UNIQUE index
> is funny because it is a constraint and an performance utility.  I see
> your point that a constraint is more ANSI standard, but because we can't

Yup.  Makes sense.  I submitted a patch which retains the difference. 
If the index is created with CREATE UNIQUE, it's dumped with CREATE
UNIQUE.  Constraint UNIQUE is treated likewise.



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: Memo on dropping practices
Next
From: Bruce Momjian
Date:
Subject: Re: Unique and Primary Key Constraints