tracker issue : CF-3035908

select a category, or use search below
(searches all categories and all time range)

Bug 72824:(Watson Migration Closure)handling timezones (tz) in cf is complicated and often misunderstood

| View in Tracker

Status/Resolution/Reason: Closed/Deferred/

Reporter/Name(from Bugbase): Paul Hastings / PaulH (PaulH)

Created: 08/29/2008

Components: Localization

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 7


handling timezones (tz) in cf is complicated and often misunderstood. it would be nice to have a setTimezone() method like setLocale() to force the server to use that tz for all it's datetime handling. 

pie-in-the-sky but it would also be nice to have the tz preserved & be able to be manipulated in the datetime objects especially as we're seeing a boatload of flex/air on the frontend.




----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3035908

External Customer Info:
External Company:  
External Customer Name: PaulH
External Customer Email: 00EE238442D680B29920157F
External Test Config: 08/29/2008



This bug has been voted..
Vote by External U.
24774 | November 10, 2011 10:39:36 AM GMT
+1 This would be a great addition to the system. I'm also thinking that if this feature is added, could it be specified at the application level, like mappings are? Just thinking aloud...
Vote by External U.
24775 | November 10, 2011 10:39:38 AM GMT
+1 vote. Working with Timezones is still to big of a PITA in CF. I'd also love the DateConvert("conversion-type", "date") to support conversion from UTC to a specific Time zone. Obviously, using the setTimezone() would convert to the correct timezone, but in an application I maintain I often need to convert times in resultset from to the correct time in each user's timezone (which means I'd have to keep calling setTimezone().) I'd much rather be able to specify the timezone in the dateConvert() function. You could do: DateConvert("conversion-type", "date", "timezone") The conversion-type would still be either local2utc or utc2local, but the optional "timezone" argument would allow you to specify the timezone to use for "local".
Vote by External U.
24776 | November 10, 2011 10:39:39 AM GMT
it seems railo has tz per "web" (whatever that means). cf9 having more granular tz control would be a real plus.
Vote by External U.
24777 | November 10, 2011 10:39:40 AM GMT
This bug has been voted..
Vote by External U.
24778 | November 10, 2011 10:39:41 AM GMT
This bug has been voted..
Vote by External U.
24779 | November 10, 2011 10:39:42 AM GMT
+1 as jvm argument cannot always be set (ex: shared hosting) +1 also for THIS.timeZone
Vote by External U.
24780 | November 10, 2011 10:39:43 AM GMT
Pretty lame that this not available. On shared hosts this is a nightmare to implement
Comment by External U.
24772 | July 01, 2012 12:42:04 PM GMT
This is now a required feature (and should be "un-deferred") due to: 1) CF10 changed behavior of dateConvert(). It now only changes the string representation of a date/time object but no longer changes the underlying numeric value. Thus, cfqueryparam sends values as local (instead of UTC) and serializeJSON() outputs values as local (instead of UTC). 2) getTimeZoneInfo() doesn't return "DSTSavings" (#CF-3037207). DST Savings is not always, and may not always be, 1 hour. Thanks, -Aaron
Comment by External U.
24773 | December 15, 2012 03:59:51 AM GMT