Hi Dimitry,

In firebird-support@yahoogroups.com, "Dimitry Sibiryakov" wrote:

> I'd suggest an additional column in table which is filled with
> uppercased, unaccented string by triggers (or application). Then you
> can use something like SELECT col FROM t WHERE uppered_col STARTING
> WITH :pre_uppered_search ORDER BY col.
> [...]

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.

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()?

Regards,
Peter Jacobi