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 get rid of non-unique indexes, I am not sure if there is really a good reason to move to UNIQUE constraints. Well, it does make the table definition and index more compact (one statement) but we split them up on pg_dump so we can load the table without the index, so it doesn't seem to be a win. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
