Subject FB2.1 Case-insensitive searching options
Author tomc7777777

We are moving to FB2.1 and were wondering on the new options available
to us regarding the above. We especially want to get rid of having to
have 'shadow upper_fieldname columns' maintained by triggers for

Anyone with any tips or recent experience with the above (proven in
the field) would be much appreciated:

1. Can we drop all upper_x columns and now use expressions indices?
2. (Pre-FB 2.5) Any character set/collations combinations that can
easily be set to get over this need?
3. A.n.other technique?

Many thanks,

p.s. all data is straight-forward ascii text (locale: GB/UK English)