[AusNOG] Q about time zones especially UTC

[Bruce Rosenberg]

Or go a step further and store all values in Unix time stamps where possible, which are UTC by nature.

Over the years I've found it's far easier to store all date/time stamps as UTS values; they are database platform independent and every major server-side programming language / framework includes functions to easily deal with them.

You'll never run into problems converting between MySQL, Postgres, Oracle or SQL Server date/time and PHP, Ruby, .Net date/time again.

And, you can pass them natively to client-side JS frameworks like JQuery, ExtJS et al and have the client format them for its timezone - no server side processing required.

-----Original Message-----
From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Martin Barry
Sent: Tuesday, November 20, 2012 8:51 PM
To: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] Q about time zones especially UTC

$quoted_author = "Alex Samad - Yieldbroker" ;
> 
> So what do ISP, Tier 1,2 providers (people who operate in multiple time
> zones) use ?

UTC. 

Store timestamps as UTC in as many places as possible, if not everywhere.
You still might hit issues with leap seconds but not daylight savings or
other fun.

Do the translation to local time in the presentation layer of any interface
used by humans.

cheers
Marty
_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog