Re: Unique and Primary Key Constraints

Поиск
Список
Период
Сортировка
От Rod Taylor
Тема Re: Unique and Primary Key Constraints
Дата
Msg-id 1026572902.30427.161.camel@jester
обсуждение исходный текст
Ответ на Re: Unique and Primary Key Constraints  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: Unique and Primary Key Constraints  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Unique and Primary Key Constraints  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Rod Taylor
Дата:
Сообщение: Re: Memo on dropping practices
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Unique and Primary Key Constraints