Dec 31, 2015; 11:15
Justin Dennis
Timezone Conversion
'morning -
I have been hitting my head against a brick wall with timezone conversion.
Right now, we do a lot of this at the SQL level in MySQL:
CONVERT_TZ("2015-12-31 23:00:00", "US/Arizona", "US/Eastern")
This works great, because it takes into account when US/Eastern means EDT
or EST while Arizona does not do daylight savings time.
I was hoping to find a list of timezones supported by the ICU library, but
no luck. In fact, their documentation seems to suggest that they don't even
address "generic" timezones like "ET", instead requiring "EST" or "EDT". I
was hoping to delegate the daylight savings time determination to someone
(e.g. MySQL, ICU, Lasso) who can do it better than me.
Our database stores all dates and times in our HQ's local timezone, which
is "ET". So every time a user enters a local time, we have to convert
before storing.
How do others deal with this issue? Thanks for any insights, and I wish
everyone a happy New Year!
- Justin
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>
Dec 31, 2015; 10:32
Steve Piercy - Website Builder
Re: Timezone Conversion