* Harald Fuchs [...] > > You could also store the number of halfhours. > > Nope. Chatham Island has an offset of +12.75 hours.
Yeah, and Kathmandu is +5.75 hours. Better avoid customers from Chatham Island and Kathmandu, then... ;) Seriously, I have implemented a timezone system once, but we only had customers in Europe, so we used full hour offsets, and it worked as intended. If you need to support all timezones, using minutes should be safe. Or you could store the number of _quarters_ of an hour... :) Anyone know of a timezone with an offset not devideable by 15 minutes? By the way, if you also need to store the offset of the server, you should use minutes or maybe even seconds, depending on your the need of your application for accurate time. That way you can adjust for servers with wrong clocks, in cases where the server is not in your own server room. -- Roger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
