|
Joe, Your experience with this would make a good "Tips and Techniques" article... JK > And I understand your preference. Checking every date by doing a CHAIN > or SETLL on a file is easy. I think part of my bias is that I come from > a scheduling background, which means I need information for periods, > rather than single days. I might have to schedule an operation to run > over 10 days, and thus I'll have to know all the working days. By > reading a one-year array once, I'm covered and I can schedule all the > work for that item. > > With a one-record per date approach, I'll be doing lots of I/O, over and > over again (unless I read the data from the file into an array, at which > point your argument about how hard it is becomes moot). > > I guess my point is that I think you need to look not only at the data > but also at how it is used when determining the normalization of a > database. > > Joe
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.