Icon View Incident Report

Minor Minor
Reported By: Adam Hair
Reported On: 4/1/2013
For: Version 4.35 Build 2
# 3839 Using Ambiguous Column References in Joins Can Result in AV

Im currently getting an access violation when I attempt to run the following query.

Simplified version of query:

Select *
From RFP R
left outer join Port DP on (Port = R.DischPort)
left outer join Port BP on (Port = R.BorderPort)



Comments Comments and Workarounds
The problem was with the ambiguous Port column references. What would happen is that DBISAM would end up trying to set the second LOJ join condition as:

left outer join Port BP on (DP.Port = R.BorderPort)

and DBISAM wasn't handling such a join condition (one with no column references for the target table of the join) properly. The workaround is to make sure that all column references in joins contain table correlation names.


Resolution Resolution
Fixed Problem on 4/2/2013 in version 4.36 build 1


Products Affected Products Affected
DBISAM Additional Software and Utilities
DBISAM CLX Client-Server
DBISAM CLX Client-Server with Source
DBISAM CLX Standard
DBISAM CLX Standard with Source
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

Image