× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: <rob@xxxxxxxxx>
>
> Another business case. A die hard native person did some time trials
and
> was stunned to find the sql faster. However he decided to stick with
> native anyway.

This is somewhat apocryphal, or at least incomplete enough to be
misleading.  For what type of operation was SQL faster?  And why did the
person stick with native?  Some people like to use native access because
they find it easier to debug 10 separate I/O statements than one
ten-line-long SQL statement.

In any event, my most recent comparisons still showed SQL being roundly
outperformed by native access for single-record chains and particularly
for single-record inserts and updates.  If you have other information,
I'd love to see it.  At the same time, I'll try to dig up those tests
and run them again.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.