I thought that AUTOINCREMENT key (called IDENTITY in SQL) should be unique and once deleted it can not reappear again. But that is exactly what is happening to me now.
In one of Pervasive older manuals I found:
"When you delete a record containing an AUTOINCREMENT key, the MicroKernel completely removes the record from the file. The MicroKernel does not reuse the deleted key value unless you specify that value when you insert another record into the file, or unless you deleted the record with the highest value."
I remember that the things were behaving like that once upon a time, but now I can not force Btrieve to forget the deleted AUTOINCREMENT key - the next inserted record will get the previously deleted one!
Or I am missing something in the configuration settings?
I have found the same behavior under 9, 9.5 and 10 versions of Pervasive SQL.
Is there a way to force the engine to use unique keys?
Start Free Trial
