for case insensitive index, you can have another column that holds lower-case
version of your original column. you can create an index on that lowercase
column and use it in your sql. you can use triggers to maintain the lowercase
column.
ali
--- On Mon, 6/23/08, Alan Burlison <[EMAIL PROTECTED]> wrote:
> From: Alan Burlison <[EMAIL PROTECTED]>
> Subject: Re: any feedback on this?
> To: "Derby Discussion" <derby-user@db.apache.org>
> Date: Monday, June 23, 2008, 4:42 PM
> Rick Hillegas wrote:
>
> > I have commented on the issue. Your latest proposal
> sounds to me like
> > DERBY-455 (expression indexes). That would be a very
> elegant, powerful
> > feature but I think that DERBY-481 (generated columns)
> entails less
> > effort and gives us most of the power of expression
> indexes. As you note
> > in your comment, generated columns have limited value
> if you don't index
> > them.
>
> How do people work around this at present? I absolutely
> *must* have
> case-insensitive indexed searches in my application.
>
> --
> Alan Burlison
> --
