Dale McDiarmid
Dale McDiarmid
any chance you could try the branch https://github.com/ClickHouse/clickhouse-go/tree/issue_727 @ns-gzhang - see if this solves it. I've added explicit close on cancel.
No, a cancelled connection was [marked as dirty](https://github.com/ClickHouse/clickhouse-go/blob/main/conn_process.go#L142) and would not be reused in the current approach. It would require two queries to effectively take the same connection from the...
so i was refering to the native interface @ns-gzhang its possible there is something in the indirection of sql/database that makes this possible. We could close the connection on ResetSession....
@ns-gzhang did the branch version with connection cancellation work?
Nice catch, will fix in 2.4.0.
This is quite tricky in native since we effectively send `INSERT INTO issue_741 (Col2, Col1) VALUES` to ClickHouse and it responds with the block it expects - this has the...
i think we'll sort the block according to the requested order. PR today.
responds with just those - this is native protocol behavior though. HTTP is different and will need a different approach.
@wizzard0 issue existed on both protocols - native and HTTP. https://github.com/ClickHouse/clickhouse-go/pull/790 fixes
there is native format and native protocol. We always use native format, but user can choose between native protocol and http.