Refactor Sqlalchemy queries to 2.0 style (Part 5)#32474
Merged
Conversation
phanikumv
added
the
full tests needed
phanikumv
force-pushed
the
sqla_metastore
branch
3 times, most recently
from
July 11, 2023 09:12
f9349e2 to
2bb4a5a
Compare
uranusjr
reviewed
Jul 11, 2023
phanikumv
force-pushed
the
sqla_metastore
branch
from
July 11, 2023 11:27
5d78baf to
26d31e4
Compare
uranusjr
reviewed
Jul 12, 2023
uranusjr
reviewed
Jul 12, 2023
Also tuple_not_in_condition since they are basically the same thing but different operator.
phanikumv
force-pushed
the
sqla_metastore
branch
from
July 12, 2023 03:34
7d6c84b to
c0d4f61
Compare
ephraimbuddy
added
the
type:misc/internal
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
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.