Mikhail Shustov

> and full protocol support are critical. @laruh what TCP protocol features do you consider critical for your case?

what about ```rust client .query("SELECT plus({val1: Int32}, {val2: Int32}) AS result") .with_param("val1", 42) .with_param("val2", 144) .fetch_one::() .await?; ```

@serprex closed by https://github.com/ClickHouse/clickhouse-rs/pull/159?

We also need to add tests for read-only user. see examples: https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-common/__tests__/integration/read_only_user.test.ts I'm not sure why you observe ` DB::Exception: (transport error: 500)` when nodejs client tests assert against an...

If the driver doesn't work with the default settings for the `read only` user, for example, because the driver changes `settings`, we need to review the list of changed settings....

I believe we need to move it to PowerBI repository. It's likely to be a lack of mapping to Decimal type with precision. see https://github.com/exasol/powerbi-exasol/blob/e16793eb666361460ab83dfb46b5cadfd2002ab3/Exasol/Exasol.pq#L195

@alimans3 please create in https://github.com/ClickHouse/power-bi-clickhouse

> Keep in mind that this should also match your ClickHouse table's primary key for optimal performance. Do we enforce the right order for filter fields? > Use bracket syntax...

> during the PowerBI "preview" of the table, Could you share your DDL? Could you inspect a column for non-UTF8 characters? see https://github.com/ClickHouse/clickhouse-odbc/issues/383#issuecomment-994834602

@slabko do we need to release #478 to close the issue ?