View Incident Report

Serious

Reported By: Bojan Sinkovic
Reported On: 2/15/2008
For: Version 1.08 Build 1

# 2553 RANGE Clause Not Working Properly with ORDER BY Query

I am trying to imitate the MSSQL TOP function in ElevateDB. I came across the RANGE clause which seems like it would do it but I am not able to use it correctly.

The following ORDER BY SQL statement returns 3 rows with values 3, 2 and 1. If I include the RANGE clause then it returns only 1 row, which is correct, but the value is unexpectedly 1 when it should be 3 (as far as I understand the RANGE clause behaviour).

SELECT id FROM DATA ORDER BY id DESC

SELECT id FROM DATA ORDER BY id DESC RANGE 1 TO 1

Resolution

Fixed Problem on 2/16/2008 in version 1.09 build 1

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 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