Hmmm.... when I put together a small test case I get the same results you do,
Peter.
In the application I am developing we periodically (in my tests every 10
minutes) query a server for data and put the results into a local database. I
had the app running over the long Christmas weekend and found that there were
duplicate keys in the database on Monday morning.
I have added a UNIQUE INDEX on the same column as the UNIQUE PRIMARY KEY and
today, having run the app all last night, I have no duplicates.
I'm not sure what could have caused the problem in the first place. It seems
quite strange.
Rich
On Tue, 28 Dec 1999, Peter Hearty wrote:
> >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
> tthe 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.
|