Results 1 to 3 of 3
Thread: Deciding on date/time storage
May 23, 2012, 03:48 #1
- Join Date
- Apr 2005
- 3 Post(s)
- 0 Thread(s)
Deciding on date/time storage
When I inherited the code base I'm working on, everything was using unix timestamps, and all the converting that goes along with that. I do quite a lot of direct database reading/manipulation, as well as scripting, so it became convenient for me to start using datetime or timestamp formats, as they're human readable.
Now, I'm starting to doubt this decision. I read this useful-if-inconclusive sitepoint article on date formats: http://www.sitepoint.com/whats-the-best-date-format/
I agree with a lot of the points. ie that a date time should be human readable (which a uts is not), and also that it should contain timezone information (which datetime does not).
Now, I'm not that bothered about internationalisation, but time zones do become an issue with daylight saving time. Ie when the clocks go back, the datetime 2011-10-30 01:30 does not tell you if this was the 1:30 before the clocks when back, or after. So don't the datetime/timestamp types miss a vital piece of information?
Am I missing something here? Or am I asking for too much out of a format?