Icon View Incident Report

Serious Serious
Reported By: Ulrich Doewich
Reported On: 7/31/2009
For: Version 2.02 Build 15
# 3052 LOAD UPDATES Statement Not Loading Tables in Proper Referential Integrity Dependency Order

I've encountered a situation where I get this error for the db that is loading the update file:

Error loading the updates for the database RCS (Unknown error occurred with the table device (ElevateDB Error #1004 The primary key constraint id_pk for the table device has been violated (Foreign keys exist which refer to the primary or unique key 10)))

On the db that generated the update there is no foreign key violation: the entry in the table with the fk relation was deleted first, then the entry from the device table.

Comments Comments
The tables are now loaded according to their dependency order, which is based upon the foreign-key constraints defined for the various tables.

Resolution Resolution
Fixed Problem on 8/5/2009 in version 2.03 build 1

Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial