Icon View Incident Report

Serious Serious
Reported By: Renato Portello
Reported On: 10/8/2007
For: Version 1.05 Build 2
# 2463 NOT IN Sub-Queries Returning Incorrect Results with Sensitive Result Sets

I found that the following query does work only if I search for 'ABP', for the other value of 'idFornitore' it return wrong values.

If I launch the following SQL, I expect an empty result, but I get the following:

Expression SpessoreCU
EPITOME 35
EPITOME 70
EPITOME 105
EPITOME 140
EPITOME 210
EPITOME 420

The first record (17) is correctly filtered out from the NOT IN clause, but not the others.

SELECT 'EPITOME', SpessoreCu
FROM Ramature WHERE SpessoreCu NOT IN
(SELECT SpessoreCU FROM CostoRamatureExt WHERE idFornitore = 'EPITOME')



Resolution Resolution
Fixed Problem on 10/10/2007 in version 1.06 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