View Incident Report

Serious

Reported By: Felix Gartsman
Reported On: 6/9/2007
For: Version 1.04 Build 1

# 2375 Optimized Partial-Length Filters Not Working Correctly in All Cases

I created a new database with a single table + index and filled 4 rows (csv export).

Now when I set the filter: name = 'îë*' I get 2 rows instead of 3! If I drop the constraint it works. If I create a view with the corresponding sql it also works.

CREATE TABLE "Basic"
(
"Name" VARCHAR(50) COLLATE "HEB" NOT NULL,
"Color" VARCHAR(50) COLLATE "HEB",
CONSTRAINT "PK" PRIMARY KEY ("Name")
)
VERSION 1
UNENCRYPTED
INDEX PAGE SIZE 4096
BLOB BLOCK SIZE 512
MAX ROW BUFFER SIZE 32768
MAX INDEX BUFFER SIZE 65536
MAX BLOB BUFFER SIZE 32768

Row Data:

"îëúá","éøå÷"
"îëåðä","àãåí"
"îëåðéú","ëçåì"
"øëáú","àãåí"

Comments and Workarounds

The issue was that the filter was not positioning itself properly on the first matching row due to the partial-length search. This same issue would also occur with a LIKE operator with a trailing wildcard.

Resolution

Fixed Problem on 6/12/2007 in version 1.04 build 2

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

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap