Paul Loyd

> Panicking in response to invalid input doesn't seem great, but it's even worse that this panic is for a valid sql query. It's a controversial statement. Generally, we should...

Sorry for the late response, there were health problems. Relates to https://github.com/loyd/clickhouse.rs/issues/44, but for SELECTs instead of INSERTs. This crate doesn't provide support for dynamic columns and whether it will...

Sadly to hear it. If you need only `SELECT`s, it theoretically can be done now, but it's a little tricky: 1. Need to request a schema 2. Need to write...

These wrappers are convenient, but `ethers_core` is much bigger than just numeric types.

You can implement `Serialize` and `Deserialize` (either by creating a custom wrapper type or using `serde(with)` attribute) in similar way as `U256` in https://github.com/loyd/clickhouse.rs/issues/48.

Columns can change, innit? In this case, there is no way to do it, because the crate is about typed struct. For dynamic types you can use https://github.com/suharev7/clickhouse-rs

@shenghaoyang, theoretically, `Row::COLUMN_NAMES` can be replaced with `fn columns() -> Vec

Good idea. I think we need to provide a more flexible interface to specify not only failovers but also shards. But even an initial simple implementation by providing multiple IP/hosts...

Has anyone found a workaround for this problem?

I tried to put together a minimal example for my case: ```rust #[test] fn loom_260() { use loom::sync::{atomic::{AtomicPtr, AtomicU32, Ordering::*}, Mutex}; // A naive concurrent slab struct Slots { head:...