Icon View Incident Report

Serious Serious
Reported By: Grzegorz Rewucki
Reported On: 4/26/2007
For: Version 1.02 Build 1
# 2335 Scalar Sub-Queries Not Returning Correct Results When Used with Sensitive Result Sets

I have additional problem with using SELECT statement in WHERE clause. The following SQL returns empty (incorrect) result set.

CREATE TABLE "KalWinOdsTab"(
"Id" VARCHAR(5), 
"Nazwa" VARCHAR(30) COLLATE "PLK",
CONSTRAINT "PK_KALWINODSTAB" PRIMARY KEY ("Id"),
CONSTRAINT "UC_KALWINODSTAB_NAME" UNIQUE ("Nazwa")
);

CREATE TABLE "KalWinOds"(
"Id" VARCHAR(5),
"Od_dnia" DATE DEFAULT CURRENT_DATE,
"Procent" DECIMAL(10, 3) DEFAULT 0.00,
"Skala" SMALLINT DEFAULT 365,
CONSTRAINT "PK_KALWINODS" PRIMARY KEY ("Id","Od_dnia"),
CONSTRAINT "FK_KALWINODS_KALWINODSTAB_ID" FOREIGN KEY ("Id") REFERENCES "KALWINODSTAB" ("Id")
);

SELECT * FROM KalWinOds
WHERE Id = (SELECT Id FROM KalWinOdsTab WHERE Nazwa = 'Test')
ORDER BY Id, Od_dnia;



Comments Comments and Workarounds
The workaround is to use an insensitive result set instead of a sensitive result set.


Resolution Resolution
Fixed Problem on 4/26/2007 in version 1.03 build 1


Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image