I'm playing around with a recently bought ElevateDB, version 1.02 on an XP-OS, considering migration of a number of hard tested applications based on DBISAM tables.

Conversion to the new format has been surprisingly simple and efficient, so up to this point I have been quite happy.

However, I have run into something, that seems like a bug. Our users perform a number of searches in some of the tables, based on setting various filters on specific fields.

Take a (simplified) table with a field "DESCR" containing the following values

ALFA 133
ALFA 160
BETA 200
BETA 220
BETA 300

Setting a filter expression DESCR LIKE 'A%', correctly gives a result of 2 records
Filter DESCR LIKE 'BETA%' gives the expected 3 records
Filter DESCR LIKE 'BETA %' (notice the space character) results in 0 (zero) records and
Filter DESCR LIKE 'BETA 2%' again gives the expected 2 records

The same results are given if I use a filter expression in the format DESCR = 'xxx*'.

I have tried to use the filter in a small test-application and using the elevateDB Manager. Results are equal in both cases.

Is this a bug - or am I missing something important??

Best regards

Paul B

Paul

I think its the trailing space issue. What datatype is the field CHAR or VARCHAR?


Roy Lambert

Paul,

<< Take a (simplified) table with a field "DESCR" containing the following
values

ALFA 133
ALFA 160
BETA 200
BETA 220
BETA 300

Setting a filter expression DESCR LIKE 'A%', correctly gives a result of 2
records
Filter DESCR LIKE 'BETA%' gives the expected 3 records
Filter DESCR LIKE 'BETA %' (notice the space character) results in 0 (zero)
records and
Filter DESCR LIKE 'BETA 2%' again gives the expected 2 records

The same results are given if I use a filter expression in the format DESCR
= 'xxx*'. >>

It's a bug.  It has to do with the trailing blank trimming during searching
combined with partial-length searches with a trailing wildcard.  A fix will
be in 1.03.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

>It's a bug.  It has to do with the trailing blank trimming during searching
>combined with partial-length searches with a trailing wildcard.  A fix will
>be in 1.03.

-- Thanks a lot for a quick reply.

Best regards,
Paul B