Austin Bonander
Austin Bonander
We can add options _beyond_ what `libpq` supports, that's not a problem. We just used `libpq` as a baseline. However, I'm leaning towards letting the user specify a custom `rustls::ClientConfig`...
I'd just have a method that takes `rustls::ClientConfig` and one that takes... I dunno, probably a [`native_tls::TlsConnector`](https://docs.rs/native-tls/latest/native_tls/struct.TlsConnector.html). If we wanted to support it in the same method then we'd need...
> We have some very large queries; I'm worried about how well clickhouse will do when it's binding potentially hundreds of server-side params. Those would be some big http requests!...
@svix-jbrown can you elaborate a little about your use of query parameters? Are you using them to insert data, or do you have, e.g., `SELECT` queries with that many different...
> I double-checked the current implementation. QualifiedIdentifier seems to be an equivalent of the following: > > ```rust > let data = client > .query("SELECT number FROM ?.?") > .bind(Identifier("system"))...
@svix-jbrown I believe we're prepared to merge this for 0.14.1 if you'd like to rebase and fix the lint error.
@vwency if you'd like to open a PR I'd be happy to take a look at it.
We're absolutely interested in adding observability across the client. The biggest question is how much we want to standardize across our various language clients (e.g. the logs and spans we...
I would also like to see something to address use cases where the ingestion rate is not uniform. The time-series events in our specific use-case are generated externally and we...