>
>
>> Will a case-insensitive SQL ORDER BY be part of the new
>> SQL parser? If so, I can wait. If not, what other workaround is there
> > (I need INDEX BY WORDS, because the nonindexed search is too slow
>> with lots of data)?
>
>Yes, this is 2 excluding things.
>At least for now, because I do not have idea how implement them both in the
>same time.
>
>Only way to have one more index.
> One for search and one for sort.
>
What about letting one sort an existing cursor? Would that work? Then
you could do a search on word indexed fields, and then once you have
them have Valentina do a sort on any field, case-insensitive.
We've talked about having Valentina sort an existing cursor before --
maybe this is a good reason to allow it?
Jon
©2001 jda |
