Icon View Incident Report

Serious Serious
Reported By: Frederick Chin
Reported On: 6/22/2018
For: Version 4.45 Build 3
# 4659 SQL WHERE Clauses that Contain LIKE Wilcard Conditions with ANDs Can Cause Incorrect Results

I have a DBISAM table with 54 records, and using the following query results in zero rows when the number of source records exceeds 53 records.

select a.*, if(a.payee<>'',a.payee,a.desc) as payeedesc
from gltran54 a
where (a.tranno like '%' or upper(a.payee) like '%' or upper(a.desc) 
like '%') and a.trandate >= '2014-01-01'
order by a.trandate, a.tranno



Comments Comments
The issue was with how DBISAM was handling the wildcards combined with a performance optimization added in 4.45 for making ANDs more efficient with set processing. The fix doesn't affect the performance optimization.


Resolution Resolution
Fixed Problem on 6/23/2018 in version 4.45 build 4


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