Always thought that a standard like ISO8601 which always stores the date and time in UTC but appends the local time zone would beneficial.
Always thought that a standard like ISO8601 which always stores the date and time in UTC but appends the local time zone would beneficial.
Sometimes you need your timestamps to be in a named timezone. If I have a meeting at 9am local time next month, I probably want it to still be at 9am even if the government suddenly decided to cancel daylight time.
unless the customer you're meeting is in another timezone where the government didn't cancel daylight time
I don't think I ever needed something like that... Since most cases don't need local time zone, why not keep two separate fields?