Icon View Incident Report

Serious Serious
Reported By: Krisztian Kepes
Reported On: 8/17/2015
For: Version 2.19 Build 3
# 4246 Case-Insensitive, Partial-Length Searches Using Non-English Collations Can Cause Incorrect Results

We have found a problem with HUN CI searching.

First time I found some new values what aren't working (Kés, Kész, ...), but next I inserted new values and the problem gone to this database.

Then I retried again in a new db, and I found one problem.

The whole thing is strange because it's hectic. So sometimes with some records I can reproduce this, but if the table changes, I will loose it.

The thing isn't limited to our software: it can be reproduced in EDBMgr. But only with special records!

The problem is around locate. If we use partial and CI search, some of them failed.

First I experienced it in table, and not in query. So I thought it based on index using.

Like always find the record, but we need to use locate, so it is just a test.


Comments Comments
The problem was with how EDB performed partial-length searches on indexes defined with non-English collations. This was reported in the past for Hungarian and German collations, and was thought to have been fixed, but certain character combinations still caused incorrect results. The previous incident report was #3249 - Partial Locates Using Certain Collations Causes Incorrect Results.


Resolution Resolution
Fixed Problem on 8/24/2015 in version 2.20 build 1


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

Image