David Busby wrote:
You should watch what you say. I know this will abuse the system, which will it abuse the least?
A database would not work because I wouldn't be able to #1 make this easy tree structure to scan #2 it will be smaller storage wise in files and in a DB with all that overhead #3 digging through the tree is faster than an index scan in mysql, postgresq or DB2 with as many records as I'll have. The projected database structure would be >=3Tb, but by using directories as my index I can eleminate much of that overhead and shring my storage requirement to a maintainable 750G. You don't learn that in programming class, you learn that building financial software for the last 10 years.
You #1 didn't have enough information to tell me how to arch. my software, #2 assumed the wrong info and made the wrong suggestion and #3 didn't provide any helpful information #4 attempted an insult on a list that is supposed to assist. Why even send your post? (don't bother with answer)
Why couldn't you implement this in a database. I can think of several easy implementations in doing so. What you have described is a simple tree.
-- Thomas T. Veldhouse Key Fingerprint: 07C7 BF05 4176 F50B A083 4542 0118 1315 761F D300 Spammers please contact me at [EMAIL PROTECTED]
-- [email protected] mailing list
