View Incident Report

Serious

Reported By: Krisztian Kepes
Reported On: 11/9/2012
For: Version 2.11 Build 2

# 3680 Simple MAX() Aggregate Queries Returning Same as MIN() Aggregate Queries with Descending Indexes

I have just tested one table, checked the deletions, and I used MIN and MAX to see what is the limit of my deletion. But I got same result in every way.

Table:

CREATE TABLE "nyomtatas_naplo"
(
"kod" INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 0, INCREMENT BY 1),
"report_nev" VARCHAR(50) COLLATE "ANSI" NOT NULL,
"kapcsolodo_kod" INTEGER,
"report_cim" VARCHAR(250) COLLATE "ANSI",
"crc_string" VARCHAR(30) COLLATE "ANSI" NOT NULL,
"data" BLOB COMPRESSION 6,
"feltoltve" TIMESTAMP NOT NULL,
"modositva" TIMESTAMP NOT NULL,
"user" INTEGER,
CONSTRAINT "kod" PRIMARY KEY ("kod")
)

Index:

CREATE INDEX "nyomt" ON "nyomtatas_naplo" ("modositva" DESC)

Query:

select max(modositva) FROM nyomtatas_naplo

Comments

The problem was that MAX() queries were not working correctly when the indexed column used for the MAX() was marked as descending.

Resolution

Fixed Problem on 11/10/2012 in version 2.11 build 3

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