|
WHY would you consider using anything other that the date datatype (other than the timestamp type)? This is even one of the new features that we don't need RPG/IV for. There is a bit of a performance hit -- see the MC articles for details -- but if you are that hurting for performance, buy a larger machine. Using the date datatype allows date manipulation that is only a dream with 8,0 numeric fields, and while you can use the *ISO MOVE option in RPG, SQL is another story, not to mention ODBC, JDBC, etc. Just my 0.02 worth. -Walden > -----Original Message----- > From: mcsnet!midrange.com!midrange-l-owner@Mcs.Net > [mailto:mcsnet!midrange.com!midrange-l-owner@Mcs.Net]On Behalf Of Dan > Swartz > Sent: Tuesday, January 06, 1998 9:59 AM > To: midrange-l@midrange.com > Subject: use of date type fields > > > We're embarking on some database design issues and I wanted to know how > others felt about the use of date type fields versus just numeric type > fields (format would be CCYYMMDD). > > What overhead (if any) would there be to convert numeric fields to date > type fields to do certain date interval calculations? > > Any suggestions would be GREATLY appreciated. > > Dan +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.