Efficient use of text-containing field

[Ed Kleban]

On 12/6/05 2:06 AM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

> On 12/6/05 5:41 AM, "Ed Kleban" <Ed at Kleban.com> wrote:
> 
>> Since you're using IndexedByWord, as you say, then to also do a sort then
>> yes, you'll need to allocate some other field.
> 
> Ed, with Valentina no need to make COPY of data.
> 
> You can just create calculated field, which will on the fly calculate value.
> And then Jon say: build index for this calculated field.
> 
> So you get best case:
> 
>     one field which keep strings
>     
>     and 2 indexes around this field.
> 
> 

Ah ha! Very cool.  Good trick to know.  I'll have to think some more about
what could be done with calculated fields.  I clearly haven't given them
sufficient consideration.  But since I'm almost always more concerned with
speed over space they aren't inherently appealing since they "sound"
expensive :)

Thanks Ruslan.