That's not actually an error. Since your timespan is across the night daylight savings changed, there is one less hour in it than there otherwise would be. That's right, the hour between 2 and 3 AM on the night of the time change is skipped. That day only has 23 hours in it. And in autumn there is a day with 25 hours in it. So... it's not an error.
Move your timespan to a timespan that doesn't include DST change and I'll bet it starts working as expected.... Also.... Any CF scheduled event set to go at 2:30AM that night also would not fire because that hour doesn't exist on that night. And it would fire twice in the fall. Trippy huh? -Cameron Wil Genovese wrote: > I have a different take on the CF timezone issues. First off our servers > are and have been adjusted for DST correctly. They shifted automatically > without issues, now() returns the correct time for our servers in the > Central timezone. I did however notice a datediff() issue. If your doing a > datediff across the spring DST time shift your get weird results that are an > hour off. > > Use this link to see the code I'm using and an example of the output. This > is on a BlueDragon server, but if you run the code on CF7 or CF8 you will > get similar incorrect values. > > http://www.wilgeno.com/duration.cfm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Server/message.cfm/messageid:6589 Subscription: http://www.houseoffusion.com/groups/CF-Server/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.10
