Can not setup client timezone
See original GitHub issueIn the conection properties did not find how to setup client’s timezone
Even starting transaction in a tab did not help:
begin;
SET TIME ZONE 'UTC';
select ..... ;
so I get wrong (not desired) results: http://joxi.ru/vAWMwOZI1L0Ejm (sorry, text is not copied)
but in the psql
I get for same query:
startdate | enddate | amount | amount | valid
------------------------+------------------------+--------+--------+-------------------------
2018-08-01 00:00:00+00 | 2018-08-02 00:00:00+00 | 14 | 14 | [2018-08-01,2018-08-02)
2018-08-02 00:00:00+00 | 2018-08-03 00:00:00+00 | 14 | 14 | [2018-08-02,2018-08-03)
2018-08-03 00:00:00+00 | 2018-08-04 00:00:00+00 | 14 | 14 | [2018-08-03,2018-08-04)
Issue Analytics
- State:
- Created 5 years ago
- Comments:20 (8 by maintainers)
Top Results From Across the Web
Can't set time zone automatically - Windows Client
Can't set time zone automatically in Windows 10 · Use Registry Editor. Run Registry Editor as an administrator and follow these steps: ·...
Read more >Troubleshooting Client Time Zone Issues
When Client Time Zone is enabled, the client passes its time zone information (not the clock time) to the server. The server obtains...
Read more >If you can't change the time or time zone on your Apple device
To do this, go to Settings > Privacy & Security > Location Services > System Services and turn on Setting Time Zone. Check...
Read more >Remote client copy - system's time zone cannot be determined
Hello, During Remote client copy , I got error "THe system's time zone cannot be determined. Enter it using STZAC" and remote client...
Read more >When I connect to a Cloud Access Software session the time ...
Ensure the time zone is correctly set on the client. A PCoIP Zero Client's time zone maybe set through the AWI or Teradici...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@serge-rider I’m not suggesting that DBeaver is changing the value stored in PostgreSQL.
I’m saying that the combination of the following two facts results in very misleading behavior with DBeaver defaults
timestamp
valuesuser.timezone
System property which affects the timezone that DBeaver translates Postgres’s UTCtimestamp
values intoTo recreate the scenario I’m describing simply launch DBeaver with a
user.timezone
of something other than UTC (anything with a non-zero UTC offset will do). Potentially your system default is already suitable.Here’s the problematic SQL
I’m in
EST
and I see2018-08-08 08:00:00
.The value you’ll see (presuming your
user.timezone
system property is not one with a 00:00 UTC offset) will NOT match the literal you entered. Even IF you specify a+00:00
offset in yourtimestamp
literal then the selected value from the last line will not display as you expect because DBeaver is converting it to youruser.timezone
.At the end of the day it simply seems misleading to convert a zero offset value to a non zero offset value and not display the offset you’ve applied.
@KES777 the issue is that DBeaver is formatting the time to your user timezone and then HORRIBLY not including the offset or timezone abbreviation in the output. You should see a timezone abbreviation in the bottom of your status bar that indicates this. This results in very confusion output from UTC datetimes from PostgreSQL as you’re running in to.
I’ve not been able to affect the
user.timezone
system property with DBeaver command line arguments in Linux.will all result in DBeaver still reporting the timezone as “EST” upon startup and formatting
Timestamps
accordingly.The only way I’ve found that can actually change DBeaver’s timezone is by editing the system dbeaver.ini file to add
-Duser.timezone=UTC
It would be a much less confusing default if DBeaver would at least put the timezone name or offset that it is applying to datetime/timestamp values when formatting them.