× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



What I especially like about date fields is that they know what they are. No arguments about mmddyy, iso, etc. No June 31, No worries about leap year. It all just works. Its a whole slew of problems that just go away. I love "duedate = %date(INVDATE) + %days(30)" and it just works.



Mark Walter wrote:
When given the chance, I like to use Date/TIme/Timestamp fields. I don't think zero date fields are an issue. Just use and check for *LOVAL. With databases being accessed in so many different ways, date fields give one more method of not having to worry about how the data is defined.

Mark Walter
Paragon Consulting Services, Inc.
IBM Certified System i Specialist
717-764-7909 Ext. 26
mwalter@xxxxxxxxxxxxxxx
www.paragon-csi.com



Mike <koldark@xxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx
12/13/2007 02:54 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
To Date or Not to Date... that is the question






I go back and forth on this internally and decided to ask the experts.
Without starting another political battle (like that won't happen), when
defining a date field, is it better to define it as a date or as a decimal
8?

What I see is:

Benefits to date:
* SQL selections on date are simple
* can easily use data BIFS

Benefits to decimal 8:
* Can have a "zero" date, a date typed field needs to be 0001-01-01
* date BIFS a bit harder to use (but not much)

What is your preference and why?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.