Reported By: Tim Young Reported On: 6/28/2019 For: Version 4.48 Build 3
# 4752SQL SELECT JOINOPTIMIZECOSTS Keyword Not Working Properly The SQL SELECT JOINOPTIMIZECOSTS keyword does not work properly in most cases because it is using incorrect sampling of candidate values from the parent table involved in the join. This results in joins not using row scans in situations where they should be, such as cases where the amount of I/O involved in an index scan would be prohibitively large.
ResolutionFixed Problem on 6/29/2019 in version 4.48 build 4
Products AffectedDBISAM Additional Software and Utilities 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