Clickhouse-connect

Latest version: v0.7.14

Safety actively analyzes 641049 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 16

0.5.23

Bug Fixes
- SQLAlchemy table reflection threw an exception for `SimpleAggregateFunction` columns. This has been fixed.
https://github.com/ClickHouse/clickhouse-connect/issues/180
- The client no longer logs an invalid warning for query types that did not return a timezone header.
https://github.com/ClickHouse/clickhouse-connect/issues/181
- Querying `SimpleAggregateFunction` columns with a LowCardinality type parameter was broken. This has been fixed.
https://github.com/ClickHouse/clickhouse-connect/issues/182
- The `query_arrow` method now correctly accepts the external_data parameter. https://github.com/ClickHouse/clickhouse-connect/issues/183
- The `query_arrow` method has been fixed for read only queries/settings. https://github.com/ClickHouse/clickhouse-connect/issues/184

New Feature
- A common setting `max_connection_age` has been added, which will ensure that HTTP connections are not reused forever (this
can help with certain load balancing issues. It defaults to 10 minutes

0.5.22

Bug Fix
- There was a critical issue when using zstd compression (the default) with urllib3 version 2.0+. This has been fixed.

0.5.21

Bug Fix
- Logging "Unexpected Http Driver Exception" only as WARNING instead of ERROR. Use the raised OperationalError if you depend on this. Thanks to
[Alexandro Sandre](https://github.com/alexandrosandre) for the fix.
- The `wait_end_of_query` setting is no longer automatically sent with inserts. This caused unnecessary buffering on the ClickHouse server file system, especially
in the case of many small inserts. It can still be added using the `settings` dictionary of the client `*insert` methods if needed for some reason.
- The query setting `use_na_values` has been renamed to `use_extended_dtypes` and now applies to all extended/special Pandas dtypes (except the Pandas Timestamp type).
Set this to `False` to limit the dtypes returned in Pandas dataframes to the "basic" numpy types. (Note that this will force the use of numpy object arrays
for most "nullable types") This should allow creating "basic" dataframes for greater compatibility. Closes https://github.com/ClickHouse/clickhouse-connect/issues/172.

0.5.20

Bug Fixes
- Fix Pandas dataframe inserts where the Dataframe index does not match the data values (after, for example, creating a new DataFrame from
a subset of the original.) https://github.com/ClickHouse/clickhouse-connect/issues/167 Thanks to [Georgi Peev](https://github.com/georgipeev) for
the report and suggested fix, and his continued stress testing of Pandas functionality.
- Compression and other control settings were not properly sent with the request if the corresponding setting was not enabled on the server.
Many thanks to [Alexander Khmelevskiy](https://github.com/khmelevskiy) for the extended investigation and subsequent fix. https://github.com/ClickHouse/clickhouse-connect/issues/157

0.5.19

Bug Fixes
- Fix quoting and escaping of array literals in server parameters. See [159](https://github.com/ClickHouse/clickhouse-connect/issues/159). Big thanks to
[Joachim Jablon](https://github.com/ewjoachim) for the report and the fix.
- Pandas and numpy Date values were incorrect for values after 2050. This has been fixed. https://github.com/ClickHouse/clickhouse-connect/issues/164
- Fixed server side parameter binding of the NULL value for Nullable types
- Added support for `no_proxy`/`NO_PROXY` environment variable. Also added support for lower case `http_proxy` and `https_proxy` variables. Note that
lower case versions have precedence over upper case versions. Fixes https://github.com/ClickHouse/clickhouse-connect/issues/163

0.5.18

Performance Improvement
- The server timezone will not be applied (and Python datetime types will be timezone naive) if the client and server timezones match
and the `get_client` apply_server_timezone parameter is True (the default). This improves performance where client and server
have the same (non-UTC) timezone. To override this behavior and always apply a server timezone to the result, use `apply_server_timezone='always'`.
This should fix https://github.com/ClickHouse/clickhouse-connect/issues/157

Page 8 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.