Home -> Community -> Mailing Lists -> Oracle-L -> More Info-Daylight Savings Problem
I'm not directly involved, just a curious bystander, but I got more information. I am working at a large electric utility and incoming readings from industrial meters record energy usage by the hour. The time stamp is on the hour (no 1:15 or 1:30 times, just 1:00). The original design had a table with all dates/hours until the sun goes nova, and foreign key relationships from this thing all over the place. The old 'virtual entity' argument won out and a date function was used instead to validate the date/time and a unique key constraint added to prevent duplicates. The problem only comes up once a year in October when 2:am becomes 1:am again. Suggested solutions were to have a smart function add a second to the time on that day only, using Grenwich(sp?) Mean Time (someone suggested that on this list), and adding a column to the key denoting this one special case. This last one is the most popular so far, as the column will always be null except for 1:am Standard Time on the last Sunday in October. Tim Sawmiller tsawmiller_at_us.oracle.com "The opinions expressed here are my own and not necessarily those of the Oracle Corporation". Received on Mon Jan 29 1996 - 15:58:23 CST
Tim Sawmiller tsawmiller_at_us.oracle.com "The opinions expressed here are my own and not necessarily those of the
Original text of this message
