-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding at_timezone feature #7708
Conversation
✅ Deploy Preview for meta-velox canceled.
|
967e216
to
459a624
Compare
std::chrono::system_clock::time_point tp{std::chrono::seconds{ts.getSeconds()}}; | ||
|
||
// Africa/Abidjan has offset +00:00 -> use this timezone to establish UTC as starting offset | ||
auto startZonedTime = date::make_zoned("Africa/Abidjan", tp); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not GMT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was using the terms interchangeably as they are practically equivalent in this context - can replace with GMT. My point was that the input time is to be interpreted at GMT, so the Africa/Abidjan timezone, with offset of +00:00, is used to construct a starting timepoint based on the input timestamp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we not use the actual string "GMT" for clarity?
@svm1 Sorry about the delay in getting back at this PR; somehow I lost the notification. Feel free to ping me on Slack if things hang around for too long. |
Thanks for looking over @pedroerp - I must apologize now, I must've missed your ping over the holiday season! After clarifying my understanding of the |
…racting UTC ts via sys_time(), init remains issue
@svm1 are you planning to get back to finish this PR? |
@pedroerp I opened a new PR for the same here - #8554. I initially split the PR into two, for the |
@svm1 sounds good, I'll check that one. Can you close this one? |
Adding at_timezone ("timestamp at timezone") feature.