What is the behavior difference of using a non-unique
index to enforce a unique/primary key constraint when
inserting a duplicate value ?
Index range scan ?
--- Brian MacLean [EMAIL PROTECTED] a écrit :
ahhh, mostly right. I found in v8.1.6 that
if I use a non-unique
index to
Title: RE: Can I partition my primary key constraint index?
I don't know. I made the non-unique index by mistake and noticed that the index did not drop when I was correcting the mistake.
-Original Message-
From: paquette stephane [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 15
To: Multiple recipients of list
ORACLE-L [EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: Re: Can I partition my
primary key
Subject: Re: Can I partition my primary
key constraint index
:
[EMAIL PROTECTED] Subject: Re: Can I
partition my primary key constraint index?
05/13/01 02:55 PM
Please respond to
ORACLE-L
Yes, Cherie, you can. When creating the primary key constraint
:
ndant.com Subject: RE: Can I partition my primary
key constraint index?
Sent by:
[EMAIL PROTECTED
Title: RE: Can I partition my primary key constraint index?
ahhh, mostly right. I found in v8.1.6 that if I use a non-unique index to enforce a unique/primary key constraint that the index does not drop when you drop the constraint.
-Original Message-
From: Vadim Gorbounov
Hello, Cherie,
Short note first - when you drop primary key the associated index will be
dropped too.
To partition the index you will create this index first and then
alter table table name add constraint index name primary key(column
list);
HTH
Vadim Gorbounov
