View Incident Report

Serious

Reported By: Charles Bainbridge
Reported On: 5/12/2015
For: Version 2.19 Build 1

# 4181 Queries Return Incorrect Results When Turning Off Standard NULL Behavior

We’ve got a bit of a puzzle here. This was spotted in 2.18b4 a couple of days ago and is still there in 2.19b1, installed this morning.

We run EDB servers with Standard NULL Behavior=0 in the server configuration .INI file – for DBISAM-like behaviour.

Consider the four select statements run against the attached database below.

Statement 1 produces a result set where only the DEADLINE column with non-NULL values is returned.

Statement 2 produces a subset of rows where DEADLINE is non-NULL and OSSTATE = 1

Statement 3 produces a subset of rows where DEADLINE is non-NULL and OSSTATE = 2

Statement 4 produces a result set that includes all rows where OSSTATE=0 irrespective of the content of DEADLINE

1) select * from iss_ordstat where deadline <= date '2015-12-31'
2) select * from iss_ordstat where deadline <= date '2015-12-31' and osstate=1
3) select * from iss_ordstat where deadline <= date '2015-12-31' and osstate=2
4) select * from iss_ordstat where deadline <= date '2015-12-31' and osstate=0

Resolution

Fixed Problem on 5/14/2015 in version 2.19 build 2

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

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap