You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.
Conversion to UTC should be performed seamlessly without needing to use a time shift.
Actual Behavior
When using the Convert to UTC option for querying a table based on UTC time with a TIMESTAMP type, the created Date object returns a time that is offset to UTC but still reported as the browser timezone, leading to the returned data being offset by the browser timezone.
Steps to Reproduce the Problem
Create use a TIMESTAMP type time column
Fill with UTC based data
Have the browser timezone be something other than UTC
Check the Convert to UTC option
The text was updated successfully, but these errors were encountered:
Hi @tanner-bruce,
I couldn't reproduce the issue -
My browser indeed isn't set to UTC time, and when I used the convert to UTC option it worked well and convert my given time to a valid UTC time.
It might be related to your plugin version, please be sure you are up to date with our most recent version (currently 2.0.1 and soon to release another one).
Beside of that, if the issue still occur, please elaborate and be more specific so I will be able to reproduce it.
Bug Report
Expected Behavior
Conversion to UTC should be performed seamlessly without needing to use a time shift.
Actual Behavior
When using the
Convert to UTC
option for querying a table based on UTC time with aTIMESTAMP
type, the createdDate
object returns a time that is offset to UTC but still reported as the browser timezone, leading to the returned data being offset by the browser timezone.Steps to Reproduce the Problem
TIMESTAMP
type time columnConvert to UTC
optionThe text was updated successfully, but these errors were encountered: