Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change type of defualts for include_deferred #33271

Merged
merged 1 commit into from
Aug 9, 2023

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Aug 9, 2023

We should change the defaults to client defaults for MSSQL compatibility The change in #32709 was not liked by MSSQL


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

We should change the defaults to client defaults for MSSQL compatibility
The change in apache#32709 was not liked by MSSQL
@potiuk potiuk added this to the Airflow 2.7.0 milestone Aug 9, 2023
@ephraimbuddy ephraimbuddy added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Aug 9, 2023
@potiuk potiuk merged commit d989e9d into apache:main Aug 9, 2023
42 checks passed
@potiuk potiuk deleted the add-mssql-drop-default branch August 9, 2023 21:00
ephraimbuddy pushed a commit that referenced this pull request Aug 9, 2023
We should change the defaults to client defaults for MSSQL compatibility
The change in #32709 was not liked by MSSQL

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
(cherry picked from commit d989e9d)
@uranusjr
Copy link
Member

Gosh no, this is exactly the thing I rejected in the original PR. Please don't.

@potiuk
Copy link
Member Author

potiuk commented Aug 10, 2023

Sure - if we know how to handle it better so that all our dbs are happy with it + offline migrations - I am super happy about server defaults. My change was based on the observation that so far none of our migrations did it. But agree that would be more consistent if we can solve all the "multi-db/sqlalchemy woes connected with it).

Or drop MSSQL which I advocated on the devlist about 3 times already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) kind:documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants