Yikes.

Why would you do this over a calculated/computed field?

The only thing I see this as doing is eating up disk space... and even
then, the overhead of the trigger would be the similar to that of the
computed field.

Jason

>
> A well-performing solution for case-insensitive orderings and searches is
> to include a proxy column for each column you want this feature for, and
> populate it with an insert and an update trigger, e.g.
>
> create trigger pop_proxy for Human
> active before insert or update as
> begin
> new.proxy_name = upper(new.name);
> end
>
> Index the proxy column.
>
> ./hb
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>