Skip to content
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.

Sign up for GitHub

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

Jump to bottom

sql: fix current_timestamp behaviour with time zone set #43012

Merged
merged 1 commit into from
Dec 6, 2019
Merged

sql: fix current_timestamp behaviour with time zone set #43012

merged 1 commit into from
Dec 6, 2019

Commits on Dec 6, 2019

  1. sql: fix current_timestamp behaviour with time zone set 

    With time zones set, current_timestamp needs to localise to the timezone
set in the context for time options, e.g. for `TIME` with `UTC+3` at
`UTC midngiht`, `current_timestamp()` should return `3am`. This was
previously not handled correctly by Timestamp, and is rectified in this
PR.

Release note (bug fix): Previously, current_timestamp would not
correctly account for `SET TIME ZONE` in the background when storing
results, storing the timestamp as `UTC` instead. This is fixed in this
PR.
    @otan
    otan committed Dec 6, 2019
    Configuration menu
    Copy the full SHA
    b78a228 View commit details
    Browse the repository at this point in the history