tomconlon7777777 wrote:

>>Firebird v2.0 allows for indexes to be defined based on expressions.
>>Thus you will be able to define an index on "UPPER( Field_NAME)" and
>>have the system use the index as appropriate.
>>
>>
>
>Its a good improvement but it doesn't satisfy the need in question.
>When users can't find some data (non-indexed) and I say "you need to
>type it is exactly as you entered it" (ok - I'm exaggerating, there is
>an UPPER() function but the truth is I don't want to incur a function
>call for every row on a large table - esp. across the wire, precluding
>use of indexes - if I don't have to).
>
>
>Tom
>
>

Tom,

I am from Brazil, I missed a lot the case/accent-insensitive search.

FB 2.0 addressed it completely !

FB 1.5 and prior have limted suport for it, you could use accent/case
insensitive but LIKE, START WITH and CONTAINING was buggy, and the index
key size was a problem too.

Believe me, it works great ! (I have been using a localized port of FB
called Firebird-PT_BR that did it for years !)

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br