FWD » Core Development » Database

This test shows that if a field is part of a leading component, then it will trim the rvalue for BEGINS:

def temp-table tt1 field f1 as char field f2 as char index ix1 f1 index ix2 f1 f2 .

create tt1.
tt1.f1 = "abc d".
tt1.f2 = "abc d".
release tt1.

def var ch as char.
ch = "abc d ".
message length(ch).

find first tt1 where tt1.f1 begins "abc d " no-error.
message avail tt1. // yes
find first tt1 where tt1.f1 begins ch no-error.
message avail tt1. // yes

find first tt1 where tt1.f2 begins "abc d " no-error.
message avail tt1. // no, not leading
find first tt1 where tt1.f2 begins ch no-error.
message avail tt1. // no, not leading

In FWD we emit either upper(tt1.f1) like 'ABC D %' in case of literals or toUpperCase(convertToSQLBegins(ch)) in case of an expression.

I can't see how to fix this properly at runtime (as we have different levels of caches either at FQL, SQL, or even FFC results), so is kind of complicated to make sure the argument is trimmed.

I suggest to emit toUpperCase(convertToSQLBegins(rtrim(ch))) for the second case and for the first case automatically rtrim the literal case: upper(tt1.f1) like 'ABC D%'

Created 10901a from trunk rev 16292. In rev 16293: If in a BEGINS LVALUE is a field part of the index used for sort, then RVALUE must be right-trimmed.

Alex, please review.

Branch 10901a was merged to trunk rev 16395 and archived.