Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When storing time zone for a given date, is there a particular advantage offered by persisting the time zone’s ID string (e.g. Joda’s DateTimeZone.getId()) versus saving the local time offset from UTC (e.g. Joda’s DateTimeZone.getOffset())?
Although Joda’s DateTimeZone and the JDK’s TimeZone appear to share ID strings, it seems that saving the offset would be more language agnostic.
The answer depends on you’re use case. The offset is language agnostic, but might need to be interpreted back to the ID for a user to pick from. Most users don’t know what they’re offset is.
On the other hand, if you’re users can be reasonably expected to know their offset, then you don’t need to interpret.
It’s more of a design decision then it is a best practice issue.