So I’ve read and understand https://www.metabase.com/docs/latest/troubleshooting-guide/timezones.html
We’re 100% UTC except for the Metabase client, which is set to Central time.
Here’s the problem, if you have a DATE in your MySQL database, like
2019-01-17, and you display it in your browser, Metabase will say
It would seem the documentation is saying “change the server timezone to central then”. I don’t think that’s a good solution. I think it’s safe to say most of us would assume when we say
2019-01-17 should be interpreted in the reader’s timezone.
Let’s say it’s Saturday 8p for me in Central time, and I ask my friend in China, “Did you go to the store today?” It’s Sunday 8am where he is. He’s not going to “where was I at today between last night at 9pm and this morning at 8am”. He’ll simply reply “No, I just woke up”.
Simply put, Metabase should not be doing converting dates to the time at midnight and substracting the offset from UTC. It should simply assume that a DATE field is always in the connection time zone.
I hope this makes sense, thank you!