Async driver support

[randomowo]

dialect mostly fully copied from sqlalchemy.dialects.mysql.asyncmy

[randomowo]

need to set sqlalchemy>=1.4.24 (because of AdaptedConnection)

[randomowo]

@xzkostyan Is there something needed from me for PR to be merged?

[coveralls]

Coverage: 83.684% (+0.002%) from 83.682% when pulling 8723077 on randomowo:async-driver-support into 35bc4e6 on xzkostyan:master.

[xzkostyan]

@randomowo the first step is green check. Good job. It's completed now. I'll take a detailed look on this PR in weekend.

[xzkostyan]

Very good!

Why do we have test "core" types (Int, Ip, date) behaviour in async version of native dialect? Isn't it redundant?

[randomowo]

Async native dialect works a little differently (at least with different drivers) from sync, and I think we should test it separately, but on the other hand, we have types testing in the driver library. So if you still think it is redundant, I can remove it.

[xzkostyan]

Async native dialect works a little differently (at least with different drivers) from sync, and I think we should test it separately, but on the other hand, we have types testing in the driver library. So if you still think it is redundant, I can remove it.

You are right, we should test it separately. But async dialect inherited from the sync one: class ClickHouseDialect_asynch(ClickHouseDialect_native):. Type processing isn't overloaded in this dialect. Async native and sync native interfaces use clickhouse-driver under the hood. It means that we are testing the same "core part" in terms of data post-processing from underlying driver. In case of native interface types are bypassed to use, in case of HTTP interface data should be converted into Python types.

That's why, IMHO @with_native_and_http_sessions is enough for type testing for tests located here: tests/types. Tests for async behaiviour are very useful.

[randomowo]

Async native dialect works a little differently (at least with different drivers) from sync, and I think we should test it separately, but on the other hand, we have types testing in the driver library. So if you still think it is redundant, I can remove it.

You are right, we should test it separately. But async dialect inherited from the sync one: class ClickHouseDialect_asynch(ClickHouseDialect_native):. Type processing isn't overloaded in this dialect. Async native and sync native interfaces use clickhouse-driver under the hood. It means that we are testing the same "core part" in terms of data post-processing from underlying driver. In case of native interface types are bypassed to use, in case of HTTP interface data should be converted into Python types.

That's why, IMHO @with_native_and_http_sessions is enough for type testing for tests located here: tests/types. Tests for async behaiviour are very useful.

ok, i'll delete it soon

[xzkostyan]

Looks good to me. Let's make linter happy.