|
ISO 8601 allows for leap seconds, just as it allows for leap years.
Does DB2 have a 'we don't need to store legitimate but rare values'
exemption? I didn't see one.
While a leap day is big enough for ordinary people to notice if it's
missing, leap seconds are utterly inconsequential for the vast, vast,
vast majority of people and businesses.
Typically for me, I used a stupid example. Let's say that a trading
partner sends me a transaction and it's stamped 2016-12-31-23.59.60 UTC.
I didn't generate it, I don't have control over the stamps they send
me. What should I do with that transaction?
Alter the incoming timestamp?
Reject the transaction?
Right now, the least worst answer seems to be that I should stop using
TIMESTAMP data types and revert to two separate columns instead: a DATE
and a TIME (which I can NULL out 'rare but legitimate' values of)? At
least then I can store the date part which will (mostly) let me answer
questions like 'how old is this invoice?'
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
