Icon View Incident Report

Serious Serious
Reported By: Tiago Ameller
Reported On: 10/27/2009
For: Version 2.03 Build 4
# 3091 Bookmarks Not Being Set Properly for Navigation of UNIQUE Constraint Indexes

Using the table creation script below, create the table.

Insert 3 rows by hand, Codigo = 1,2,3 - Nombre = 'uno', 'dos', 'tres'.

Set the active index to the Unique_ScanCode index that is created for the ScanCode UNIQUE constraint, and you will see duplicated rows appear in any grid that is connected to the table.

SCRIPT
BEGIN
 EXECUTE IMMEDIATE 'CREATE TABLE "trMateri"
(
"CodigoLog" INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 0,
INCREMENT BY 1) NOT NULL DESCRIPTION ''Código interno'',
"Codigo" INTEGER NOT NULL DESCRIPTION ''Código Cecome'',
"Nombre" VARCHAR(20) COLLATE "ESP_CI_AI" NOT NULL,
"ScanCode" SMALLINT,
"Comentario" CLOB COLLATE "ESP",
"Favorito" BOOLEAN DEFAULT False     NOT NULL,
"UnidadesDefecto" INTEGER DEFAULT 0   NOT NULL,
CONSTRAINT "ixPrimary" PRIMARY KEY ("CodigoLog"),
CONSTRAINT "Unique_Codigo" UNIQUE ("Codigo"),
CONSTRAINT "Unique_ScanCode" UNIQUE ("ScanCode") --> Here is the problem
)
DESCRIPTION ''Materiales tanto de entrada como salida''
VERSION 1
UNENCRYPTED
INDEX PAGE SIZE 4096
BLOB BLOCK SIZE 512
PUBLISH BLOCK SIZE 512
PUBLISH COMPRESSION 0
MAX ROW BUFFER SIZE 32768
MAX INDEX BUFFER SIZE 65536
MAX BLOB BUFFER SIZE 32768
MAX PUBLISH BUFFER SIZE 32768';
END



Comments Comments
The problem was EDB was not setting the bookmarks properly for UNIQUE constraint indexes, resulting in the SetToBookmark method not working properly when trying to position the dataset on the correct row.


Resolution Resolution
Fixed Problem on 10/28/2009 in version 2.03 build 5


Products Affected Products Affected
ElevateDB Additional Software and Utilities
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

Image