That makes perfect sense, Set. I guess for example a customer name field
should have an uppercase equivalent in the database, since it isn't all that
uncommon for the users to want to browse all customers in a list, but for
something like classifications I could use the upper(fieldname) method
because there rarely are more than tens or low hundreds of records.

Thanks,
Antti Kurenniemi

----- Original Message -----
From: "Svein Erling Tysvaer" <svein.erling.tysvaer@...>
To: <ibobjects@yahoogroups.com>
Sent: Thursday, September 14, 2006 12:51 AM
Subject: Re: [IBO] Case-insensitive sorting


> As long as the result set is small, this solution works nice (and you
> should always try to get small result sets). But expression indexes is
> something new with Firebird 2 (I think), that certainly isn't possible
> with Firebird 1.5. Hence, you cannot use any index with UPPER.
>
> That's why I think IBO's facility with ColumnAttribute NOCASE and a name
> for an uppercase equivalent of the field in question often is the best
> solution. Adding a before insert trigger that populates this field
> whenever you insert or update is very simple and with marginally more
> work than the OrderingItems suggested below, you get the possibility for
> indexed searching (and combining this with OrderingItems is a good idea).
>
> Set
>