View Incident Report

Serious

Reported By: Terry Swiers
Reported On: 7/3/2017
For: Version 2.26 Build 1

# 4531 Single-Table SELECT Statement with MAX Expression and WHERE Clause Returns Incorrect Results

I'm seeing a simple max statement fail in 2.26 that works in 2.25. The following query returns a null value. If I remove the where portion of the statement, it does return the proper value.

select max(number) from invoice where transtype = 1

Comments

This issue would only occur if the column being used with the MAX expression was indexed and there was a WHERE clause present.

Resolution

Fixed Problem on 7/3/2017 in version 2.26 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