mbtolou

thanks. I rewrote the 'PushBatch' function I created an event for the error mode that returns the corresponding record of the error I also created a test for the above...

I checked it. It is very useful. Thanks

```sql SET allow_experimental_live_view = 1; DROP TABLE IF EXISTS test.lv; DROP TABLE IF EXISTS test.mt; CREATE TABLE test.mt (a Int32) Engine=MergeTree order by tuple(); CREATE LIVE VIEW test.lv AS SELECT...

I have been using this code for some time and it works for me without any problems. One of the features of this code is that it continues to work...

in your driver does not work . in other driver like postgres work correctly.

For `where 1=1` 10.0.0.138:9000, queries 1000, **🔴QPS: 28.922**, RPS: 0.000, MiB/s: 0.000, result RPS: 0.000, result MiB/s: 0.000. 0.000% 0.024 sec. 10.000% 0.033 sec. 20.000% 0.033 sec. 30.000% 0.034 sec....

> I will change the selection criteria then thank. Can't you determine features the first time you connect?

 thank.

> Thank you for performance comparison - I will change the selection criteria then > > `SELECT version()` us used when opening new connection to determine which features the server...

`Unique Key Constraint` is great idea.