dbTalk Databases Forums  

difference in Rushmore from FoxPro 8 to 9

comp.databases.xbase.fox comp.databases.xbase.fox


Discuss difference in Rushmore from FoxPro 8 to 9 in the comp.databases.xbase.fox forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Kevin Clark
 
Posts: n/a

Default difference in Rushmore from FoxPro 8 to 9 - 10-20-2004 , 03:19 PM






I'm wondering what the differences are in Rushmore optimization from
FoxPro 8 to FoxPro 9. I recently upgraded to FoxPro 9 and found that
some queries take quite a bit longer. For example the following
query:

SELECT * FROM invbody WHERE ALLTRIM(billlname)+ALLTRIM(billfname)=tmp

is optimizable for a table in FoxPro 8 but not in FoxPro 9.
Everything else is the same as far as I know.

Kevin Clark
Seton Home Study School

Reply With Quote
  #2  
Old   
Cy Welch
 
Posts: n/a

Default Re: difference in Rushmore from FoxPro 8 to 9 - 10-20-2004 , 05:38 PM






Kevin Clark wrote:
Quote:
I'm wondering what the differences are in Rushmore optimization from
FoxPro 8 to FoxPro 9. I recently upgraded to FoxPro 9 and found that
some queries take quite a bit longer. For example the following
query:

SELECT * FROM invbody WHERE ALLTRIM(billlname)+ALLTRIM(billfname)=tmp

is optimizable for a table in FoxPro 8 but not in FoxPro 9.
Everything else is the same as far as I know.

Kevin Clark
Seton Home Study School
Unless you have an index tag with that expression in it, it's not
optimizable in any version of Foxpro I have worked with. Optimization
requires that VFP be able to find an index tag that matches the search
criteria.

--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com


Reply With Quote
  #3  
Old   
Rick Bean
 
Posts: n/a

Default Re: difference in Rushmore from FoxPro 8 to 9 - 10-20-2004 , 05:46 PM



Kevin,
It's never a good idea to compare performance of a released product with a beta. Beta's aren't usually optimized, and may even have additional overhead for better tracking of failures by the official beta testers.

Unless you have an index on ALLTRIM(billlname)+ALLTRIM(billfname), I don't believe it'll be "optimal" in any version of VFP!

Rick

"Kevin Clark" <KevClark64 (AT) hotmail (DOT) com> wrote

Quote:
I'm wondering what the differences are in Rushmore optimization from
FoxPro 8 to FoxPro 9. I recently upgraded to FoxPro 9 and found that
some queries take quite a bit longer. For example the following
query:

SELECT * FROM invbody WHERE ALLTRIM(billlname)+ALLTRIM(billfname)=tmp

is optimizable for a table in FoxPro 8 but not in FoxPro 9.
Everything else is the same as far as I know.

Kevin Clark
Seton Home Study School

Reply With Quote
  #4  
Old   
Kevin Clark
 
Posts: n/a

Default Re: difference in Rushmore from FoxPro 8 to 9 - 10-21-2004 , 10:10 AM



I do have an index on that file using ALLTRIM and I was doing a select
based upon exactly the criteria of the index. FoxPro 8 did optimize
the query and took a fraction of a second to return results. FoxPro 9
did not optimize the query and took quite a while to return results.

The problem was resolved by creating another index just on BILLNAME
and then redoing the select. That query was optimized. Not really a
problem in the long run, just somewhat of a surprise that FoxPro 8
would optimize a certain query and FoxPro 9 would not. But as was
stated, 9 is a beta version.

Kevin Clark

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.