|
One thing, though (and this is starting to look like time to transfer the thread to the RPG list):
We did determine that writing a duplicate key to a file (and allowing it to fail) was a real killer on speed. Is there a "cheap" way to check for a duplicate key without writing, and that works when you're trying to read the file sequentially even as you're adding to it?
I vaguely remember something about the relative costs of different record-level/native database operations. I don't remember whether it was on this list, or the RPG list, or in a magazine, or a Redbook, or elsewhere, but I do remember something about examples that did exactly the same thing in different ways, and ran at dramatically different speeds.
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
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.