InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

ok, so from your reply i gather that UNIQUE PRIMARY KEY will prevent dups
from being added if the primary key is composed of a single column. 

is there any point (ie. performance, etc) in defining a UNIQUE INDEX on the
primary key column?

-----Original Message-----
From: Peter Hearty [mailto:peter.hearty@ceasar.demon.co.uk]
Sent: Tuesday, December 28, 1999 9:52 AM
To: instantdb@smartcard.co.uk
Subject: Re: UNIQUE PRIMARY KEY in iDB 3.12


>unless i'm misreading your reply, you don't seem to have answered the
>question.

You're right - I misread the question. I just tried a simple test with 3.12:

e drop table tmp;
e create table tmp (int1 int unique primary key);
e insert into tmp values (1);
e insert into tmp values (1);

...and got the expected exception. Perhaps anyone reading this who knows of
the problem could send a modified script to illustrate the point.

Regards

Peter Hearty
Instant Computer Solutions

To unsubscribe from this list, please an send
email to 'majordomo@smartcard.co.uk' with the text
'unsubscribe instantdb' in the message body.
To unsubscribe from this list, please an send
email to 'majordomo@smartcard.co.uk' with the text
'unsubscribe instantdb' in the message body.