Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 2 of 2 total |
Unique constraint not checked |
Tue, Feb 27 2007 8:11 PM | Permanent Link |
"Ole Willy Tuv" | create table test (c1 integer not null)
insert into test values (1) insert into test values (1) alter table test add constraint pk_test primary key (c1) alter table test add constraint uc_test_c1 unique (c1) Both ALTER TABLE statements execute without errors on the constraint violation. Another and separate issue is that the second unique constraint definition is invalid even if the table did not contain duplicate rows, since only one unique constraint can be defined on the same set of columns. Ole Willy Tuv |
Wed, Feb 28 2007 9:21 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ole,
<< Both ALTER TABLE statements execute without errors on the constraint violation. >> Same issue as your other two posts. << Another and separate issue is that the second unique constraint definition is invalid even if the table did not contain duplicate rows, since only one unique constraint can be defined on the same set of columns. >> EDB doesn't currently prevent this, since there really is no great harm in allowing it. However, I'll add it to the list. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 09:18 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |