Some years ago I developped a relational database that was faster than
Filemaker.
There were about 700000 records... FMP just chocked on it. HC stacks choked
after
12 MBs of data where in...
The trick was to split the interface/engine from the records which were in
turn split
into categories/levels, where any category was another stack.
This keeps the searches real fast. The smaller the file, the better...
Secondly, I knew already where the categories to be searched were so I had a
table
of doubly linked references between records. This allowed to browse the
database at
any point in seconds (Filemaker too over 15 minutes PER search)... This is
basic
computer science... Search for binary trees, etc... doubly-linked records...
It's all in how you design your database... Access times were all under 2
seconds
even from the cd media!
The reverse of the medal was that importing the records and linking the
records took
over 3 days of work non-stop on a Mac 8500 with HC 241. But it doesn't mean
that
a real time program couldn't do it real fast. MC being much faster will also
help.
Visit us at http://www.clearstream.com
IMPORTANT MESSAGE
Internet communications are not secure and therefore Clearstream International does not
accept legal responsibility for the contents of this message.
The information contained in this e-mail is confidential and may be legally
privileged. It is
intended solely for the addressee. If you are not the intended recipient, any
disclosure,
copying, distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful. Any views expressed in this e-mail are those of the
individual sender, except where the sender specifically states them to be the views of
Clearstream International or of any of its affiliates or subsidiaries.
END OF DISCLAIMER
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
