peter,
unless i'm misreading your reply, you don't seem to have answered the
question.
"You are correct though, making it a UNIQUE PRIMARY KEY should enforce
uniqueness".
rich says he did exactly that and still got dups. did you mean to say he
should create a UNIQUE INDEX?
john cummings
-----Original Message-----
From: Peter Hearty [mailto:peter.hearty@ceasar.demon.co.uk]
Sent: Tuesday, December 28, 1999 2:38 AM
To: instantdb@smartcard.co.uk
Subject: Re: UNIQUE PRIMARY KEY in iDB 3.12
Rich
AFAIK, InstantDB has always allowed duplicate primary keys (see faq.html).
You are correct though, making it a UNIQUE PRIMARY KEY should enforce
uniqueness.
Regards
Peter Hearty
Instant Computer Solutions
-----Original Message-----
From: Rich Coad <rich@isyndicate.com>
To: instantdb@smartcard.co.uk <instantdb@smartcard.co.uk>
Date: 27 December 1999 16:26
Subject: UNIQUE PRIMARY KEY in iDB 3.12
>I have a table defined with a UNIQUE PRIMARY KEY on one column. I just
noticed
>that InstantDB 3.12 seems to be allowing multiple inserts of rows with the
same
>key. I don't believe this was happening with iDB 3.11
>
>Has anyone else seen this problem? Will creating a unique index on the
column
>workaround the problem?
>
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.
|