TimeZone problems
avraam-inside opened this issue · 7 comments
The code I run in R (via RClickhouse) and the result (wrong, timezone left +3 hours)
|
The same code that I run in Tabix and the result (correct, timezone left +0 hours)
What is it? Why? Obviously, this is not a ClickHouse issue, but a JDBC driver issue.
UPD: Together with @tridelt in the correspondence below, we found out that there is a problem, but it is not in JDBC, because Clickhouse driver does not use it
Hi @avraam-1997 ,
thanks for raising an issue. I don't understand why this would be a JDBC driver issue.
Would you be so kind and elaborate?
Yours
Tridelt
Hi, thank you for your prompt response)
Of course I will explain
I use the same code in DBeaver and get the same error:
RClickHouse and DBeaver combine only 1 element - both go through the JDBC driver, while Tabix uses HTTP
At the same time, the function works correctly via HTTP.
At a minimum, the function has a "timezone" parameter and the data changes exactly in Tabix when it is used, while in R or DBeaver there is no reaction
Additional example with 'Asia/Yekaterinburg':
Hi @avraam-1997 ,
I appreciate the effort to help find the root of the issue, but RClickhouse doesn't rely on Java Database Connectivity (JDBC). No java here.
Yours
Tridelt
Hi @tridelt
Okay, so RClickHouse doesn't use Java. You should know better)
But what is interesting, it is similar with problems in JDBC (DBeaver exactly uses JDBC)
And the problem with timezones still exists in RClickHouse
Hi @avraam-1997
regardless, thanks for taking the time to open an issue here.
May I ask if you have you also opened an issue for this problem at dbeaver? If yes, would you mind linking it here?
Yours
Luca
Hi @tridelt
Created a request in the JDBC driver under DBeaver: ClickHouse/clickhouse-java#604
I don't know how to link it, this is the first time I've raised the issue on github(
And thank you for your time!
Thanks! 😃