Refactor Sqlalchemy queries to 2.0 style (Part 3) #32350
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phanikumv
added
the
full tests needed
phanikumv
requested review from
ryanahamilton,
ashb,
bbovenzi and
pierrejeambrun
as code owners
|
Same MSSQL error as we saw in main earlier today |
ephraimbuddy
force-pushed
the
sqlalchemy_changes
branch
from
f122eb8 to
270467f
Compare
ephraimbuddy
approved these changes
Jul 5, 2023
uranusjr
approved these changes
Jul 5, 2023
|
@potiuk can we merge this now |
|
Oh absolutely :) |
ephraimbuddy
added
the
type:misc/internal
Merged
bbovenzi
reviewed
Jul 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a continuation of the effort to refactor the queries to sqlalchemy 2.0 (Re-applying the revert done in #32343 by applying the label
full tests needed)cc @ephraimbuddy @uranusjr @potiuk
related: #28723
^ 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.rstor{issue_number}.significant.rst, in newsfragments.