×
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.
On 22-Apr-2015 12:56 -0500, Brian May wrote:
I agree it is the 1940 to 2039 window. Honestly, the "correct" way
to fix it will be to migrate all dates into true date data types.
This is not a small "fix". This will most likely be a major
overhaul, but in the end, you will know it is done correctly.
To be sure, even if all dates were stored with the DATE data-type,
the _same issue_ with date values falling outside the window can occur.
If the presentation-format for a DATE data-type value allows for only
a two-digit year, then the same failure should transpire to prevent
mis-inference of would be an otherwise _ambiguous_ value. A complete
fix might require that no date ever be represented with a two-digit
year, or that when such a presentation were desirable, a window
appropriate to the date information being presented would need to be
used instead of the 1940-2039 window.
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
