View Incident Report

Serious

Reported By: Richard Harding
Reported On: 7/22/2010
For: Version 2.03 Build 17

# 3253 Queries that Return Sensitive Result Sets Not Matching Ascending/Descending ORDER BY Properly

I have a table which looks something like the following. The queries below both produce the result set in DESCENDING EpisodeDate order. The execution plan for both queries stated "The result set was ordered using the index ceClientDateIND".

CREATE TABLE "ClientEpisode"
(
"ID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 281, INCREMENT BY 1) NOT NULL,
"ClientID" INTEGER NOT NULL,
"EpisodeDate" TIMESTAMP NOT NULL,
<more stuff>
CONSTRAINT "cePrimaryKey" PRIMARY KEY ("ID")
)

CREATE INDEX "ceClientDateIND" ON "ClientEpisode" ("ClientID", "EpisodeDate" DESC)
CREATE INDEX "ceClientIND" ON "ClientEpisode" ("ClientID", "EpisodeDate")


SELECT * FROM ClientEpisode ORDER BY ClientID, EpisodeDate ASC
SELECT * FROM ClientEpisode ORDER BY ClientID, EpisodeDate DESC

Comments and Workarounds

The workaround is to set RequestSensitive to False so that the result set is insensitive.

Resolution

Fixed Problem on 7/23/2010 in version 2.03 build 18

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