4 ms·
Erp. This sentence made me wince. Times don't have timezones - places have timezones. The idea that time handling is made easier by attaching timezones to time
by jameshart 8y ago
Erp. This sentence made me wince.
Times don't have timezones - places have timezones. The idea that time handling is made easier by attaching timezones to times is the cause of so many headaches. Correct time handling involves understanding place - the place where things happen, the place where the user is observing them from, the place where a clock displays a particular time.
- nsxwolf 8y agoAs well as when these observations happened or will happen in and from these places, as the rules themselves will change over time.
- flarg 8y agoI guess it depends on if the event concerned only happens at one place, such as a clinical site visit, or many places, such as a global call
- da_chicken 8y agoYeah, that's kind of an issue with the ANSI standard. It specifically allows time with time zone. Some RDBMSs only support datetimes (timestamps) with time zone, but if you want to aim for complete ANSI compliance you're supposed to allow time with time zone. PostgreSQL, which allows that data type, specifically points out in the doc that you shouldn't use it: > The type `time with time zone` is defined by the SQL standard, but the definition exhibits properties which lead to questionable usefulness. In most cases, a combination of `date`, `time`, `timestamp without time zone`, and `timestamp with time zone` should provide a complete range of date/time functionality required by any application. https://www.postgresql.org/docs/current/static/datatype-datetime.html https://www.postgresql.org/docs/current/static/datatype-date...
- fanf2 8y agoYes! I have an old rant about iCalendar being wrong for not modelling place: https://fanf.livejournal.com/104586.html https://fanf.livejournal.com/104586.html