Dale McDiarmid
Dale McDiarmid
For: - DateTime64 - `2022-08-14 17:23:12.679127111 +0800` OR `2022-08-14 17:23:12.679127` - DateTime - `2022-08-14 17:23:12 +0800` OR `2022-08-14 17:23:12` - Date - `2022-08-14 +0800` OR `2022-08-14` Keep it simple -...
(2) - yes i think this makes sense - you would insert `2022-08-15` in this case. if the user retrieves and sets the timezone they will get the original date....
k @DGuang21 lets go for a precompiled regex pattern. If people use strings they accept this will be the slow path. We'll need to document as such.
> If no tz is set for time.Time{} or string, use the client tz. For time.Time{} this is not possible since nill tz means UTC. There is no way to...
I suspect i know why this is happening - the `PrepareNamedContext` is effectively building a batch. It expects the VALUES to be passed as part of the Exec not as...
Apologies i meant to take a look at this. You can't insert using JSONEachRow since we use native format by design - this isn't clickhouse-client. We're opinionated on the insert...
Any reason you can't just use MaxOpenConns=1?
Also we'd strongly advise using temporary tables - I know other ETL tools e.g. dbt clickhouse, does this but its far from recommended practice. The table will be in memory...
e.g. otherwise we miss updates such as https://github.com/ClickHouse/ch-go/pull/175
Will test this prior to after https://github.com/ClickHouse/clickhouse-go/issues/623 for the string layer.