Icon View Incident Report

Minor Minor
Reported By: Praveen
Reported On: 7/13/2007
For: Version 1.04 Build 5
# 2411 DISTINCT Queries Returning Incorrect Results with Sensitive Query Result Sets

I've migrated my DBISAM v3.30 database to ElevateDB 1.04 B5. Below DDL statements are for same table in DBISAM and ELEVATEDB.

The column 'db_table_name' has table names all in UPPERCASE and fields 'level_name' and 'field_name' in LOWERCASE.

In Dbisam, the following queries return the correct results, but in ElevateDB they do not.

DBISAM
----------
CREATE TABLE IF NOT EXISTS "TEMP"
(
  "db_table_name" CHARACTER(30) NOT NULL,
  "level_num" INTEGER NOT NULL,
  "field_name" CHARACTER(30),
PRIMARY KEY ("db_table_name","level_num") COMPRESS NONE
LANGUAGE "ANSI Standard" SORT "Default Order"
);

ELEVATEDB 1.04 B5
-----------------------
CREATE TABLE "TEMP"
(
"db_table_name" VARCHAR(30) COLLATE "ANSI" NOT NULL,
"level_num" INTEGER NOT NULL,
"field_name" VARCHAR(30) COLLATE "ANSI",
CONSTRAINT "PK" PRIMARY KEY ("db_table_name", "level_num")
)

DBISAM
------

"SELECT DISTINCT db_table_name FROM TEMP" - returns distinct db_table_name.

ELEVATEDB 1.04 B5
-----------------------

"SELECT DISTINCT db_table_name FROM TEMP" - doesn't work. All values are returned.



Comments Comments and Workarounds
The workaround is to set the TEDBQuery.RequestSensitive property to False for VCL applications, and to request a static result set for DAC applications.


Resolution Resolution
Fixed Problem on 7/14/2007 in version 1.04 build 6


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

Image