Re: Unique and Primary Key Constraints

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Rod Taylor <rbt(at)zort(dot)ca>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unique and Primary Key Constraints
Date: 2002-07-13 15:11:40
Message-ID: 200207131511.g6DFBem26134@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rod Taylor wrote:
> 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.

Yes, very nice.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-13 16:53:16 Re: Memo on dropping practices
Previous Message Rod Taylor 2002-07-13 15:08:21 Re: Unique and Primary Key Constraints