Icon View Incident Report

Serious Serious
Reported By: Charles Bainbridge
Reported On: 8/15/2018
For: Version 2.28 Build 5
# 4678 Certain Un-Optimized Conditions Not Evaluating Properly when Standard NULL Behavior Off

We're running EDB (currently 2.27b7) with StandardNullBehavior switched off, trying to maintain previous DBISAM behaviour with strings. We've recently discovered that numeric columns containing NULL will satisfy a test for less than 0 in a WHERE clause. It works as expected (NULL does not satisfy < 0) when we switch StandardNullBehavior on.

Comments Comments
The un-optimized operations that were incorrect were: <, <=, =, <>, >=, >, [NOT] BETWEEN, and [NOT] IN.

Resolution Resolution
Fixed Problem on 8/16/2018 in version 2.28 build 6

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 PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial