Re: Use case for a "case insensitive equals" qualifier
Re: Use case for a "case insensitive equals" qualifier
- Subject: Re: Use case for a "case insensitive equals" qualifier
- From: Lon Varscsak <email@hidden>
- Date: Wed, 24 Feb 2016 18:08:55 -0700
Hmm, it would be interesting if there was an alternative, but really the problem lies in the database. Any wildcard type searches (at least that start with a wildcard) are not likely to use indexes and cause a table scan. If your database supported the concept of having case-insensitive indexes, then I would think it would be pretty trivial to implement in your own qualifier. In Sybase (the database I use mostly) you can create a functional index (an index based on a function), but it’s the equivalent creating a second column that’s always lower and maintaining an index on it. The difference being that the database maintains it for you (which is usually annoying for EOF).
I’ve always wanted a better way to do this too.
-Lon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden