Icon View Incident Report

Serious Serious
Reported By: Don Potts
Reported On: 6/14/2010
For: Version 2.03 Build 14
# 3229 Parameters Not Working Correctly in Correlated Sub-Queries

It appears there is some strange behavior with parameters (see SQL below).


WORKS:

SELECT CLAIM."Print" FROM CLAIM
WHERE CLAIM.PIN IN (SELECT DISTINCT ALLPATI.PIN FROM ALLPATI WHERE CLAIM.PIN=ALLPATI.PIN AND ALLPATI."Type" = 'MM')
AND CLAIM."Date" >= :date1 AND CLAIM."Date" <= :date2
AND CLAIM.Remaining > 0.00
AND CLAIM.Policy1 like :pol1

DOES NOT WORK:

SELECT CLAIM."Print" FROM CLAIM
WHERE CLAIM.PIN IN (SELECT DISTINCT ALLPATI.PIN FROM ALLPATI WHERE CLAIM.PIN=ALLPATI.PIN AND ALLPATI."Type" = :datype)
AND CLAIM."Date" >= :date1 AND CLAIM."Date" <= :date2
AND CLAIM.Remaining > 0.00
AND CLAIM.Policy1 like :pol1

PARAM
NAME:  datype
TYPE:     varchar
VALUE: MM
MODE:  IN



Comments Comments
The problem was that EDB was not correctly setting a flag that tells itself to execute the correlated sub-query repeatedly for each row in the parent query, but only when parameters were present in the sub-query. This issue was caused by the fix for incident #3209.


Resolution Resolution
Fixed Problem on 6/16/2010 in version 2.03 build 15


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

Image