I agree, but then, I know this is true if you use a SQL engine backend.
But if you use a DBF, how is that handled?
I mean, in order to SELECT from a DBF you either open with order 0 first
and then issue the select statement or you do not open it first, but
just do the select directly.
In both cases, you open the table. Now, does the select statement
operate on the server or it must bring the data to the local machine and
then run the sql command? In the last case it would be slower the bigger
is the quantity of records in the table.
And I stress the fact that I am dealing with a large DBF table.
[NF] Soccer World Cup
BTW, now that the Netherlands are out of the picture, we look forward to
face the Germans. Cross my fingers :-)
Rafael Copquin
El 09/07/2014 17:25, Stephen Russell escribió:
On Wed, Jul 9, 2014 at 11:04 AM, Dave Crozier <[email protected]> wrote:
Top is slow because the whole of the index (either temporary or permanent)
has to be either downloaded or created on the client machine. In many cases
the whole of the table. Hence normalising it and creating proper incxes to
filter records using Rusmore is quicker.
----------------
You still need to download the cdx to use it. Indexes are better than a
tablescan that is for sure. Having large tables on a sever RDBMS is much
better because you only communicate with the API and not with the actual
data file itself.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
