Icon View Incident Report

Serious Serious
Reported By: Terry Swiers
Reported On: 4/3/2010
For: Version 2.03 Build 9
# 3183 Computed Columns Not Evaluating Properly

There appears to be an error with EDB 2.03b9 unicode in D2009 indexing a computed column. The issue appears to be with the computed column going from having a value to being null, which results in the record being indexed with the previous value rather than the new null value.

In the attached data, is returning incorrect results when running a query with criteria against a computed column.

Run the following query against the database then then look at the 4th record returned, the one with serialnum = 105. The generated column in question is called InStockCode, and the query above should not have returned this particular row because the value of the computed column is NULL for this record.

If you drop the InStockCode index and then recreate it, the results will be correct. After you have done that, edit any of the where InvNum = 0 and ItemGUID is null to set InvNum to 1 and then ItemGUID to any value, post the change, and then re-run the query. The value in the InStockCode column will now be null but will still be returned in the result set.

select * from serial where instockcode = 'SERIAL'

Comments Comments
Some changes were made in 2.03 Build 9 to improve the performance of computed column evaluation, and this was the cause of the bug.

Resolution Resolution
Fixed Problem on 4/6/2010 in version 2.03 build 10

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