virtuals fields / ViSQL

[Ruslan Zasukhin]

On 1/14/05 5:08 PM, "Olivier" <vidal_olivier at yahoo.fr> wrote:

> I agree.
> 
> olivier
> 
> Le 14 janv. 05, à 15:39, Robert Brenstein a écrit :
> 
>> But having index-by-words set but being not in effect IS
>> confusing/misleading.
>> 
>> This is why I am suggesting that it becomes an independent flag: one
>> flag (index) controls normal indexing and another flag
>> (index-by-words) control word indexing. When both are set, the latter
>> (higher functionality) wins.
>> 
>> I think this would make things clearer for developers.

Think about this behavior.

I have field (Indexed + ByWords)

Now I want set index OFF for some time, then return it back.

So I do

        fld.Indexed = false.

        ...

        fld.Indexed = true.

Now in 2.0, the first line DO NOT remove flag IndexByWords (1.x did).
So the second line is able __correctly__ return back THE SAME index kind.

Even do not have idea how todo this in 1.x.
* You need self get and save flag IndexByWords ?
* and flag Unique?
* and for each field if you do this for several fields.


----------------
I want underline, that in 2.0 we have REMOVE several such
    
    "automatic things"

We think this is more correct way.
Because if developer DID NOT ask build index for a field,
Then search must be NOT indexed.



-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------