Icon View Incident Report

Minor Minor
Reported By: Jon Lloyd Duerdoth
Reported On: 5/3/2004
For: Version 4.05 Build 1
# 1684 Canned Query Result Sets Are Being Defined with a Unique Primary Key from the Source Tables

I can't find info as to how "select... into" sets the fields included in the primary index.

I had expected that it would have just been RecID but it seems to be related to the primary index of the selected tables.

Comments Comments
DBISAM was trying to emulate the primary key of the first table in the FROM clause as much as possible. For single-table selects, it was completely duplicating the primary key if the selected fields allowed for it, including the uniqueness constraint. This was causing problems when the canned result set was manipulated further by adding new records with duplicate keys. The canned result sets now no longer maintain any unique constraints. However, they do maintain ordering in a similar fashion as before.

Resolution Resolution
Fixed Problem on 5/6/0004 in version 4.06 build 1