On 24 Jun 2003 at 12:43, peter_jacobi.rm wrote:

>> I'd suggest an additional column in table which is filled with
>> uppercased, unaccented string by triggers (or application). Then you
>
>This may be a typical example of premature optimization, but I
>thought it would be clever to avoid this solution because it would
>need two indices for fast access.

Yes, if you need fast access. Using UPPER() you can't make thinks
fly because it expel the possibility to use an index at all.

>And another point on this approach: Am I right in assuming that
>I can use a computed column instead of a physically stored
>column, when using Firebird 1.5? I then would have to provide
>an UDF TOUPPERNOACCENT()?

What for? You can order by UDF and group by it. You can't build an
index on it to speed the selects up.

SY, Dimitry Sibiryakov.