virtuals fields / ViSQL

[Ruslan Zasukhin]

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

>> This will be correct
>> 
>> string1=new vstring("string1",38, EVflag.fIndexed +
>> EVflag.fIndexByWords)
>> string2=new vstring("string2",38,EVflag.fIndexed,"string1")
>> 
>> 
>> String1 - is indexed AND index is by words
>> String2 - is indexed and it is method
>> 
> 
> ok, that's works.
> But I does not understand why it needs there to put "string1" indexed.
> 
> We have a string field. For this string field, we want two indexs:
> indexbyword + indexed.
> 
> In Valentina 1:
> 
> We put, for the string field, "indexbyword".
> Then we created a second string field with for method :  the first
> string field + flag indexed.
> Logic.

:-) in fact in 1.x for method you can skip indexed!


> Why in Valentina 2, we have to put the flag indexed in both fields?

Because you WANT TO HAVE that both fields have INDEX. Right?

And you want to have for f1 index by words.,
For f2 regular index.


> In ViSQL, I think that there is a problem with the methods.
> I have a string field which is a method, "string2".
> In ViSQL, if I launch " SELECT * FROM table1 Where string2=' xxx ' :
> OK, no problems, it finds.
> 
> But if I launch " SELECT * FROM table1 ORDER BY string2 ", ViSQL
> indicates "Field string2 not exist".
> While this query works in my application.

Strange.

Look into window Structure of ViSQL.
Do you see both fields ?


-- 
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
-------------------------------------------------------------