|
>> Now if you're still storing years as 2-digits in your database, and
depending on the window to determine the century, *then* you've got a
problem if the window changes.
"still storing ..." - what about those folks who decided to implement
"real" dates in the database? The value is stored as a number of days (so
the full 4 digits are there) but if I chose to use DATFMT(*MDY) when I
defined the database then I'm in trouble if the system changes the window.
Right now any dates in the 1940 - 2039 range are valid as *MDY and work
just fine - but if the window changes to (say) 1960 - 2059 then if I read
one of those records with a date in the 1950s then "boom".
This is why I said I thought it would need new DATFMT options - I don't
believe you can just change the meaning of the existing ones.
Jon Paris
Jon.Paris@e400.com
www.e400.com - A new wave of iSeries and AS/400 Education
+---
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.
midrange.com
