Icon View Incident Report

Serious Serious
Reported By: Abdulaziz Jasser
Reported On: 7/20/2007
For: Version 1.04 Build 6
# 2417 ALTER TABLE ADD COLUMN AT With 0 As Position Causes Internal Column Usage Instead

Our application keeps adding/updating/deleting fields based on the business requirements. So, we have a way to manage that. There is no problem with that. What happened since build 5 is every time the application deletes the table and reinserts the values again the values of the new integer field that was created by code gets incremented!!


The field was created using this statement:

ALTER TABLE "TB_Users" ADD COLUMN SkinIndex Integer DEFAULT 0 AT 0;



Comments Comments and Workarounds
ElevateDB was allowing the 0 position and not adjusting it to 1, and this caused it to use the internal RowID column instead of the desired column. The column positions are 1-based, and the workaround to the issue is to make sure that you use 1 instead of 0 for the first column. With the fix, any time a position less than 1 is specified, it is automatically adjusted to 1 and inserted at that position.


Resolution Resolution
Fixed Problem on 7/21/2007 in version 1.05 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image