- Do not reuse expired connections (
ConnMaxLifetime) #892 by @iamluc - Extend default dial timeout value to 30s #893 by @jkaflik
- Compression name fixed in sendQuery log #884 by @fredngr
- Client info specification implementation #876 by @jkaflik
- Better handling for broken connection errors in the std interface #879 by @n-oden
- Document way to provide table or database identifier with query parameters #875 by @jkaflik
- Bump github.com/ClickHouse/ch-go from 0.51.0 to 0.51.2 #881
- Flag connection as closed on broken pipe #871 by @n-oden
- Buffered compression column by column for a native protocol. Introduces the
MaxCompressionBufferoption - max size (bytes) of compression buffer during column-by-column compression (default 10MiB) #808 by @gingerwizard and @jkaflik - Support custom types that implement
sql.Scannerinterface (e.g.type customString string) #850 by @DarkDrim - Append query options to the context instead of overwriting #860 by @aaron276h
- Query parameters support #854 by @jkaflik
- Expose
DialStrategyfunction to the user for custom connection routing. #855 by @jkaflik
- Close connection on
Cancel. This is to make sure context timed out/canceled connection is not reused further #764 by @gingerwizard - Fully parse
secureandskip_verifyin DSN query parameters. #862 by @n-oden
- Added tests covering read-only user queries #837 by @jkaflik
- Agreed on a batch append fail semantics #853 by @jkaflik
- Fix in batch concurrency - batch could panic if used in separate go routines.
The issue was originally detected due to the use of a batch in a go routine and Abort being called after the connection was released on the batch. This would invalidate the connection which had been subsequently reassigned.
This issue could occur as soon as the conn is released (this can happen in a number of places e.g. after Send or an Append error), and it potentially returns to the pool for use in another go routine. Subsequent releases could then occur e.g., the user calls Abort mainly but also Send would do it. The result is the connection being closed in the release function while another batch or query potentially used it.
This release includes a guard to prevent release from being called more than once on a batch. It assumes that batches are not thread-safe - they aren't (only connections are).
- Don't panic on
Send()on batch after invalidAppend. #830 - Fix JSON issue with
nilif column order is inconsisent. #824
- Patch release to fix "Regression - escape character was not considered when comparing column names". #828
- Support for Nullables in Tuples. #821 #817
- Use headers for auth and not url if SSL. #811
- Support additional headers. #811
- Support int64 for DateTime. #807
- Support inserting Enums as int8/int16/int. #802
- Print error if unsupported server. #792
- Allow block buffer size to tuned for performance - see
BlockBufferSize. #776 - Support custom datetime in Scan. #767
- Support insertion of an orderedmap. #763
- Decompress errors over HTTP. #792
- Use
timezonevstimeZoneso we work on older versions. #781 - Ensure only columns specified in INSERT are required in batch. #790
- Respect order of columns in insert for batch. #790
- Handle double pointers for Nullable columns when batch inserting. #774
- Use nil for
LowCardinality(Nullable(X)). #768
- Align timezone handling with spec. #776, specifically:
- If parsing strings for datetime, datetime64 or dates we assume the locale is Local (i.e. the client) if not specified in the string.
- The server (or column tz) is used for datetime and datetime64 rendering. For date/date32, these have no tz info in the server. For now, they will be rendered as UTC - consistent with the clickhouse-client
- Addresses bind when no location is set