The database does include in that /complexity/, the ability to
specify the ordering of duplicate key values; e.g. LIFO, FIFO, FCFO,
in DDS. Not all accesses to database data are via query, so
realize that non-SQL & non-query interfaces used to read-by-key can
actually effect a read-order to reflect whatever was specified as
the [build]duplicate-key-order rule(s).

I didn't notice that the originator specified that DDS was involved, and
responded with SQL on my mind. Besides, if the files had had that
specified, I don't think the question would have been asked. Right?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"An intellectual is a man who takes more words than necessary to tell more
than he knows."
-- Dwight D. Eisenhower


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.