Incorrect timezone handling when escaping a datetime-aware object

[krokoziabla]

Describe the bug
Suppose you have a table:

CREATE TABLE foo
(
    `timestamp` DateTime('UTC')
)

It contains some data. Let the maximum timestamp be 1546300800 (2019-01-01 00:00:00 UTC).
Suppose then that your CH installation resides in Moscow, so its TZ value is "Europe/Moscow"

Then you run the query using clickhouse-driver:

client.execute(
    "SELECT * FROM foo WHERE timestamp = %(timestamp)s",
    {"timestamp": datetime.datetime.fromisoformat("2019-01-01 00:00:00+00:00")})

But then a bad thing happens. This piece of code translates your timestamp to server's timezone Europe/Moscow and the resulting query SELECT * FROM foo WHERE timestamp = '2019-01-01 03:00:00' returns nothing, because as mentioned in CH's manual string values are treated in column's timezone, not server's one.

To Reproduce
See above

Expected behavior
I guess the driver has to deal with timezones more accurately. Treating timestamp string values in server's timezone may be correct if the type of column is not timezone-aware. But if the column has the explicit timezone set then it's obviously wrong to use the server's timezone for conversions.

Versions

• clickhouse-driver 0.2.6
• server 22.8.20.11
• python 3.11

[hellais]

For what it's work I am currently replacing the timezone information with None to workaround this bug.

It's probably quite important to fix this in light of the recent deprecation in python 3.12 of datetime.utcnow() which used to return time in utc without timezone information (see: https://blog.miguelgrinberg.com/post/it-s-time-for-a-change-datetime-utcnow-is-now-deprecated)