Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
English
A big problem
Message
From
24/01/2000 08:30:51
 
 
To
20/01/2000 13:34:20
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Fórum:
Visual FoxPro
Category:
Programação, sintaxe e comandos
Título:
Miscellaneous
ID da thread:
00317456
ID da mensagem:
00321595
Views:
24
>>>
>>>
Glad to hear that. But wait, 1 million records also seemed a lot to me before :) Now seeing the size is "only" 25 Mb I think it could be faster :) What about utilizing indiviual indexes instead of that one based on getexpr() ?
>>>
>>>
if seek(padl( m.VALVEGROUP, 10 ), "myTable", "myTag") ;
>>> and seek(padl( m.SIZEINC, 10 ),"myTable", "myTag1") ;
>>> ...
>>>endif
>>>
>>>* Futher nonconverted indexes could prove valuable
>>>* Faster integer indexes and even bintoc() indexes
>>>if seek(m.VALVEGROUP,"myTable","myTag") ;
>>> and seek(m.SIZEINC),"myTable", "myTag1") ;
>>> ...
>>>endif
VFP is kind enough to cut "if" testing on first failure. It's hard to say w/o testing. Building m. values for seek (if not directly saying table1.valvegroup is possible) seem to be the overheading (as far as I remember tcKeyField was a combined value). Yet it might be shorter than to create huge indexes. And indiviual indexes once built could stay there to make consequent updates ligthning fast :)
>>>IMHO in any case seek() method would be faster and doesn't need the disk space as SQL method does :)
>>>Cetin
>>
>>
>>I here what your saying. I was trying to achieve a standard approach and until this table my approach did work well - honest ;-)
>>
>>This would avoid creating the compiled list of existing entries and new entries in the first instance. Although I would have to create a new index each time for each field for the view (that may take a little time) but as you say once it is done it should be very fast.
>>
>>I'll give it ago
>>
>>By the way what is 'IMHO'?
>
>
Discard my previous message Jason or you'd lose great time. I was incorrect about how it would be interpreted. Instead a seek from view to table could benefit existing table "expr" tag.
>
>In My Humble/Honest Opinion : It's on UT acronyms list. If you enable "Show Acronyms" then it displays expanded :) - (But I think if it wasn't enabled for nonPUTM).
>Cetin

I'm sorry but you've lost me on this one "Instead a seek from view to table could benefit existing table "expr" tag."
Previous
Next
Responder
Mapa
View

Click here to load this message in the networking platform