On 9/30/2019 9:45 PM, dmccunney wrote:
On Mon, Sep 30, 2019 at 11:38 PM Ben Collver <bencoll...@riseup.net> wrote:
Ralf Quint wrote:
On 9/29/2019 7:10 PM, dmccunney wrote:
What would you be benchmarking?
I would benchmark a set of tasks performed on an identical data set.
For example, importing the data, doing a bunch of inserts, deletes,
random selects, etc.
I think what you would essentially be benchmarking would be I/O performance.
SQLite is a full SQL compliant relational DBMS implemented as a single
library. dBASE and FoxPro were, IIRC "hierarchical" DBMS products.
Depending on what you are benchmarking this sounds like an apples and
oranges comparison.
Yes comparing SQlite to dBASE or FoxPro is comparing apples and oranges,
more like apples and potatoes actually...
I thought FoxPro and Paradox were relational databases that could run in
protected mode. I recall doing joins in Paradox using QBE.
IIRC. Paradox met that description. FoxPro organized data as sets of
files to improve performance on small databases. Up to v2.5, FoxPro
was a flat file database. In v2.6, Visual FoxPro added the ability to
treat the collection of files as a relational database. Visual FoxPro
2.6 was the last version. MS had shifted focus to Access. See
https://www.alvechurchdata.co.uk/hints-and-tips/fox101data.html
FoxPro, in all versions AFAIK, used basically the same database
structure as dBASE, but incompatible indexes, which used a different
technology and hence were incompatible. And the basic user interface as
well as the programming language it provided was so similar to that of
dBASE, that Ashton-Tate filed a lawsuit against FoxPro. And after that
lawsuit was dropped on urging of the DoJ (with rumors that Microsoft
greased the wheels), A/T was bought by Borland and FoxPro was bought up
by Microsoft...
IIRC, while FoxPro derived from FoxBASE by Fox Software, which in turn
derived from Ashton Tate's dBASE III, I don't believe FoxPro or
Paradox used the dBASE programming language and were not Xbase
products, though I believe they could import existing dBASE database
files.
As mentioned in another reply, Paradox is a totally different case, with
no relation to dBASE.
FoxPro used not only the basic database file format, but also the same
basic programming language as dBASE (I know people who transferred their
application from dBASE IV to FoxPro to take advantage of the faster
indexes) but also added a lot of proprietary commands, which meant that
FoxPro programs were not backwards compatible with dBASE. FoxPro also
included its own compiler option, which made using a separate tool like
Clipper unnecessary...
(I have Paradox and the manuals, but they are not currently accessible
and I can't Look Stuff Up.)
see above...
And yes, Protected mode was pretty much a requirement. I note SQLite
for DOS was built using DJGPP, which means you need something like a
386 with a memory extender loaded to run it in DOS. I doubt this will
run on an 8088/8086 in Real Mode.
dBASE II and III definitely do, I am not sure right now about dBASE IV,
it could be that this required at least an 80286...
Ralf
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
