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
I use Postgres for storing timestamp with timezone for some columns (timestamptz type). When I download the query results in CSV, the timezone information is missing. I can confirm that timezone info in CSV was there in Redash v7. It is also there if I download the results in Excel format for Redash v8.
Steps to Reproduce
Run some query which produces timestamp in results. For example, in Postgres, one can run this query:
SELECT NOW();
Download the result in CSV format. The timestamp value will not have timezone information. For example, my CSV contents after running the query in Step 1 were as below:
now
2020-04-21 20:49
Excel format file had the contents as below:
now
2020-04-21T20:49:00.224+07:00
Why do you consider this to be a bug?
It seems like the CSV just stores local timezone and the precision is also less (there is no seconds info). This can be very confusing if someone is accessing Query results in other timezone, or comparing query results of multiple timezones.
What did you expect to happen instead?
Just like in Excel format, the CSV format should also have timezone information for timestamp columns.
Technical details:
Redash Version: 8.0.2
Browser/OS: Chrome/Ubuntu 18.04
How did you install Redash:
The text was updated successfully, but these errors were encountered:
Issue Summary
I use Postgres for storing timestamp with timezone for some columns (
timestamptz
type). When I download the query results in CSV, the timezone information is missing. I can confirm that timezone info in CSV was there in Redash v7. It is also there if I download the results in Excel format for Redash v8.Steps to Reproduce
SELECT NOW();
Excel format file had the contents as below:
Why do you consider this to be a bug?
It seems like the CSV just stores local timezone and the precision is also less (there is no seconds info). This can be very confusing if someone is accessing Query results in other timezone, or comparing query results of multiple timezones.
What did you expect to happen instead?
Just like in Excel format, the CSV format should also have timezone information for timestamp columns.
Technical details:
The text was updated successfully, but these errors were encountered: