Icon View Incident Report

Minor Minor
Reported By: Heiko Knuettel
Reported On: 9/18/2008
For: Version 2.01 Build 5
# 2799 Using the RANGE Clause with Sensitive Result Sets Can Result in Incorrect Results

I think I found a bug when using a WHERE clause and RANGE.

Example: table has 2000 rows, filtered 400 Rows, and I set a range from 1 to 100. Now I am not seeing 100 records, but e.g. only 15 records...I think those, who match the filter criteria in the first 100 records of the unfiltered table.

Comments Comments and Workarounds
The fix for this incident report is a breaking change. EDB now forces an insensitive result set whenever the RANGE clause is used, and the documentation for sensitive result set requirements has been updated to reflect this.

Resolution Resolution
Fixed Problem on 9/20/2008 in version 2.02 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