4 ms·
This is bad advice. If you convert the timezone you're now taking on the risk that your conversion was incorrect. You also lose the valuable information of the
by ed312 7y ago
This is bad advice. If you convert the timezone you're now taking on the risk that your conversion was incorrect. You also lose the valuable information of the source time zone. UTC isn't perfect and is _far_ from the only viable timezone for a given domain.
- xwdv 7y agoNope. You shouldn’t be doing your own timezone conversions. If you are storing a time into a database the database should be handling the conversion of your date to UTC. If you care about the original timezone store that elsewhere. Do not make one piece of data serve two different functions.
- dwild 7y ago> If you care about the original timezone store that elsewhere I think that was his point, that you should always care about the original timezone and thus keep it.
- hobs 7y agoSaying "We might have bugs" isnt a good reason to reject a proposal. Generally you store an offset/name of the zone, which then isnt losing the valuable information about the source zone - if you dont do this you are right, this will fall down almost immediately.