Re:Timezone updates need to be fixed
by vemv on Thursday January 28, 2016 @12:51PM
(#10989821)
I retract my opinion - the approach is clearly correct for that business domain.
The key difference is here:
> The thinking is that if a client is shopping for a class in a different timezone, why would we convert the class's time to the client's timezone? It makes no sense.
Roughly speaking, basically there are two kind of apps:
- apps where datetime values need to be localized ("this message was sent at 18:00")
- apps where datetime values need to reflect a fixed timezone ("we will meet in Madrid, at 18:00 local time")
Re:Timezone updates need to be fixed
by Khao on Thursday January 28, 2016 @01:05PM
(#10989945)
In our app, everything that's a timestamp (invoices, payments, registering to an event, sending messages, create/update timestamps, etc..) is stored in UTC. Having both depending on the use case is really the best for us.
The key difference is here:
> The thinking is that if a client is shopping for a class in a different timezone, why would we convert the class's time to the client's timezone? It makes no sense.
Roughly speaking, basically there are two kind of apps:
- apps where datetime values need to be localized ("this message was sent at 18:00")
- apps where datetime values need to reflect a fixed timezone ("we will meet in Madrid, at 18:00 local time")