AFAIK, InstantDB has always allowed duplicate primary keys (see faq.html).
You are correct though, making it a UNIQUE PRIMARY KEY should enforce
Instant Computer Solutions
From: Rich Coad <firstname.lastname@example.org>
To: email@example.com <firstname.lastname@example.org>
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
>that InstantDB 3.12 seems to be allowing multiple inserts of rows with the
>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
>workaround the problem?
To unsubscribe from this list, please an send
email to 'email@example.com' with the text
'unsubscribe instantdb' in the message body.