I see. Good point. On Fri, Jan 23, 2009 at 7:42 AM, Paul Hastings <p...@sustainablegis.com>wrote:
> John M Bliss wrote: > > Concur. datetimes in the DB should all be in the same TZ and then > converted > > to local TZ, as needed, for output. > > not quite. the problem is that cf sees all datetimes as being in the server > tz. > if the server's tz has DST then dates from any user tz that's not the same > as > the server & falls on the DST cusp will simply never exist (ie they get > rolled > into DST). this will happen any time cf touches a datetime, ie, coming > from/going into the db, calendar math, whatever. best bet is the server in > UTC > or go thru the trouble of using epoch offsets. > > or even better ask adobe to add a setTimezone() method to cf ;-) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:318396 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
