2008/8/18 Ton Voon <[EMAIL PROTECTED]>: > The user is a customer who is a sysadmin on Solaris. He's setting the > server's timezone to CET. We have our catalyst application starting up with > this default server timezone and it is failing because the CET timezone is > not recognised in DateTime.
On the best practice front: I always try to store any and all times as UTC for the app and then turn them into local time for the users on the fly. Hence every user has a timezone associated with them in the DB, which defaults to something reasonable. Doing this you can ignore the timezone of the server as it becomes irrelevant. If you do use the server's timezone then expect oddness if you ever deploy to another server in another timezone. This does make the presentation logic harder due, but makes the backend so much easier, especially comparisons etc. Also it means that all users see the time in their own timezone which is a nice touch. This may not be appropriate to your app, but if it is I recommend it. Cheers, Edmund.