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
Thanks for the report! It's true that by default clickhouse-connect returns timezone naive ClickHouse columns as UTC times. For other query_* methods you can override the timezone on the client side by using the query_tz parameter, but there is a bug in that parameter is not exposed for query_df. I'll get a fix for that in the next week or so.
In any case I think it makes sense to create setting that respects the server timezone, so we'll add that functionality in the next release as well. Just a warning that timezone conversions in Python are somewhat expensive, so I'd be inclined to leave the default for such a setting to use the current behavior of returning timezone naive UTC times regardless of server timezone.
Driver does not apply server timezone when selecting dateTime column
Query: select timeZone()
Answer: Europe/Moscow
Code example
clickhouse-connect and/or ClickHouse server logs
Configuration
Environment
ClickHouse server
The text was updated successfully, but these errors were encountered: