Has anybody come up with a good method to handle Daylight Savings Time
"anomalies"? The problem: we have rows that have date/time as part of a
unique key. How would one elegantly handle incoming data, on that blessed day
in October when we get an extra hour of sleep, that has a duplicate key
because the info being recorded happened at 1:00am EDT and also at 1:00am EST?
I would hate to have an extra field indicating DST just for something happens
only once a year. Any ideas?
Tim Sawmiller
tsawmiller_at_us.oracle.com
"The opinions expressed here are my own and not necessarily those of the
Oracle Corporation".
Received on Thu Jan 25 1996 - 14:51:01 CST
