David Blain

> > Currently the version of the common sql provider is 1.17.1, I suppose this now will have to change to 1.18.0? If so how do I do this for...

> > Currently the version of the common sql provider is 1.17.1, I suppose this now will have to change to 1.18.0? If so how do I do this for...

I have something weird going on with mysql integration tests, this PR hasn't changed anything (directly at least) related to MySQL: ``` Warnings saved into /files/warnings-operators-mysql.txt file. =========================== short test...

@eladkal @potiuk I think the dialects are ready, what do you guys think? A new feature within this PR is that if the developer doesn't need to specify the target_fields...

> That's a big one. There are two comments here: > > 1. We are rethinking packaging/ providers/plugins APIs and very likely we are going to have several different "types"...

> Also - for reference see this PR from @jscheffl : > > Original PR: #41729 > > It has been closed when all the "split" PRs have been merged)...

I now have some error regarding an invalid import, but other test cases also import the same without any issues: ``` ________ ERROR collecting providers/tests/common/sql/hooks/test_sql.py _________ ImportError while importing test...

> Needs rebase now. Do you think additional PR will be needed once [43747](https://github.com/apache/airflow/pull/43747) is merged? Because then only the dialects will be here and the adapted corresponding hooks. We...

@potiuk For the backward compatibility, I was wondering maybe we should ditch it here, and only support it for Airflow 3.x The dialects will work any for native hooks like...

> Yes. it could be Airflow 3-only feature. As long as the providers as a whole work for Airlfow 2 as well and we document it well I agree this...