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
When working under dotnet 6.0 with date fields, a timezone error appears. When the same code is running under dotnet 5.0, such an error does not occur.
The text was updated successfully, but these errors were encountered:
Versions of ClickHouseClient for .Net 6 and .Net 5 have different approaches for handling time zones. The version for .Net 6 uses new time zone conversion API. The version for .Net 5 relies on TimeZoneConverter.
There may be two possible reasons for a time zone error in the .Net 6 version of ClickHouseClient.
An application is running in the invariant globalization mode. In this case very limited set of time zones is supported by the runtime both on Windows and on Linux.
An application is running on Windows and is not in the invariant globalization mode. In this case there are several time zones which are supported by ClickHouse but are unknown to the runtime.
Here is the query for a list of time zones supported by ClickHouse:
SELECT*FROMsystem.time_zones
I checked time zones from this list on different version of ClickHouseClient running on Windows.
Here are time zones which are not supported in the ClickHouseClient version for .Net 5 (Windows):
When working under dotnet 6.0 with date fields, a timezone error appears. When the same code is running under dotnet 5.0, such an error does not occur.
The text was updated successfully, but these errors were encountered: