> On Aug 24, 2017, at 6:28 PM, Keith Medcalf <[email protected]> wrote:
> 
> Timezone is something that is applied and removed at the User Interface level 
> and should never exist below the presentation level.

There are cases where the timezone needs to be preserved in the data model 
because it can be important to know the local time corresponding to the event. 
A common example is email: the Date header includes a timezone, so that the 
recipient can tell what the local time was. For instance, it can be significant 
to know whether it was 2PM or 2AM local time when a co-worker sent you a grumpy 
email about a bug. (The same goes for other communications like blog posts and 
chat messages.)

—Jens
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to