January 21, 2019 at 9:17 pm
Comments posted to this topic are about the item The Lost Time
January 22, 2019 at 3:00 am
I am not a great fan of daylight saving and here in the UK would prefer to stay on BST the whole year round. When I commuted it made no difference as I left in the dark and came home in the dark.
For a time I worked on telephone networks and call logging. Clock changes were a nightmare as you needed to sync the network (easier these days with central clocking) and catch erroneous data. One example was someone would make a 2 minute call and be logged as having made one for 1h 2m or 23h 2m depending which way the clocks went. It was all sorted in the end but showed things had not been thought through!
January 22, 2019 at 3:07 am
I agree.
5ilverFox
Consulting DBA / Developer
South Africa
January 22, 2019 at 3:11 am
I totally agree. Time is essentially represented as a scale data type starting from an agreed zero point. When the clocks change you are effectively removing or adding units from the scale in a rather arbitrary fashion. It doesn't feel right to me at least from a data perspective.
SELECT DATEDIFF(HOUR,'2019-03-31 00:00:00', '2019-03-31 02:00:00')
This returns 2 hours but there are not 2 hours between 12AM on the 31st of March and 2AM on the 1st of April. There is only 1 hour because 1AM effectively does not exist as the clocks skip to 2AM.
A scale should be a scale not a scale with bits taken out here and added in there!
You could just as easily say from 31st of March 2019 we all just get to work an hour later and leave work an hour later.
It also completely messes with my biological clock!
January 22, 2019 at 3:59 am
I was brought up on a farm and the argument was always about daylight hours for working. Being an annoying child I could not see if you were limited to seven hours of daylight whether it mattered if you started at 7:00, 8:00 or 9:00!
January 22, 2019 at 4:20 am
mjh 45389 - Tuesday, January 22, 2019 3:00 AMI am not a great fan of daylight saving and here in the UK would prefer to stay on BST the whole year round. When I commuted it made no difference as I left in the dark and came home in the dark.For a time I worked on telephone networks and call logging. Clock changes were a nightmare as you needed to sync the network (easier these days with central clocking) and catch erroneous data. One example was someone would make a 2 minute call and be logged as having made one for 1h 2m or 23h 2m depending which way the clocks went. It was all sorted in the end but showed things had not been thought through!
BST was a temporary wartime measure first brought in in world war one , rescinded after the war , re-introduced in world war two and retained afterwards. GMT on the other hand was the scientifically determined time as a result of astronomical observation so if anything we should do away with BST and remain on GMT as anything else is a social artefact .
January 22, 2019 at 5:01 am
I've always agreed with Steve that DST is a waste of time. Now Europe is talking about getting rid of it, with individual countries getting to choose which time they take. That could lead to situations where you travel East but the clocks go back or vice-versa. I'm also torn between which I would prefer - it getting light stupidly early in the morning in the summer - or it staying dark awfully late in the morning in the winter.
Am starting to wonder if it's not so bad after all.
January 22, 2019 at 5:16 am
Agreed. Daylight Saving Time serves no purpose and id needlessly problematic.
January 22, 2019 at 6:10 am
For business it causes problems.
The one reason I like it is the extra hour o daylight after work. Thats a big plus
My personal feeling is that time sensitive business should ALL be run on UTC in the background, only converting to local time for display purposes.
...
-- FORTRAN manual for Xerox Computers --
January 22, 2019 at 6:20 am
I agree, but then, at least for some states like Indiana, it brings up a new debate as to which time zone the state or area should permanently move to. In Indiana, high noon by the sun is around 12:30. So no matter which zone you go to, you are still off a half hour. It was not too many years ago, Indiana exempted itself from DST, but the argument was "What time is it in the neighboring state". You cannot win for loosing in my state.
January 22, 2019 at 6:20 am
I would not be bothered if the UK stuck on GMT or BST although if we went to permanent BST I would prefer to go in to and finish work an hour earlier in the summer.
Maybe the UK should have a referendum? Arghh,, no I did not mean it! Only joking! 🙂
January 22, 2019 at 6:58 am
In the UK I think they should just move the clocks forward half an hour in March and then never move it again. I expect that everywhere there is daylight saving time the same could be done.Assuming there was ever any point in changing clocks it would mean it was never more than half an hour wrong (whatever that means). Also wish they wouldn't call it daylight saving time because clocks can't save daylight.
January 22, 2019 at 6:59 am
GMT
January 22, 2019 at 7:08 am
At a hospital, we literally turn off, or make unavailable, our major systems from 1:00 am to 2:00 am on the big day and go to paper. For example, if a patient comes in 1:30 am we admit at 1:30 am. When someones comes in 1/2 hour later, voila, its now 1:00am. Which pat came in first ? Pain in the neck.
January 22, 2019 at 7:16 am
I prefer the extra hour in the evening rather than when I would rather be sleeping. It is a pain from a technology standpoint, but hardly the worst. I've had a chance to use the SQL Server 2016 time zone capabilities, and they are very helpful towards dealing with this.
Viewing 15 posts - 1 through 15 (of 38 total)
You must be logged in to reply to this topic. Login to reply