I've run into the following issue:
My app has multiple users from multiple timezones. In the majority of
cases, I want datetime columns to take into account the user's
timezone. This works fine.
However, for *one* particular datetime field, I want users to enter
the arrival date & time of a flight that is arriving into a country in
a different timezone to the user's timezone. Hence I don't want any
timezone conversion done on this particular field.
e.g. a user in Germany enters the data for a flight that will arrive
in New Zealand on January 1st at 2:00pm. When a different user views
this data, I want it to say 2:00pm, regardless of the user's timezone.
I don't see that the datetime_select helper allows me to specify a
timezone for the time I am selecting; but anyway, I don't want the
user to have to enter a timezone.
I suppose the easiest (only?) solution is to store the data in
separate date and time fields in the database, and use separate
date_select and time_select helpers.
Any comments? Should this functionality be something that datetimes /
datetime_select should support?