-
Notifications
You must be signed in to change notification settings - Fork 106
[Issue 171] Improve sqlalchemy dialect backward compatibility with 1.3.24 #173
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
Merged
Changes from 5 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ba55341
(1/x) SQLAlchemy 1.3 cannot parse our connection string so http_path,
b5c1dd9
(2/x) SQLAlchemy 1.3 automatically tries to create CHECK constraints …
52f3c5e
(3/x) SQLAlchemy 1.3 exposes the underlying connection / cursor with
01ec014
(4/x) SQLAlchemy 1.4 introduced different semantics for the select()
be758d7
(5/x) Pandas requires sqlalchemy 1.4 to work. So we can skip this for…
c29899a
(6/x) Add smoke tests for inspector behaviour
27dfff6
(7/x) Smoke test failed for 1.4 because receive_do_connect only writes
f606e59
Black the code
1c3d080
Format tests
ca5dee7
Update changelog
1f69254
Sync branch 'main' into issue-171
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops. This change belongs in a separate commit. Basically: version 1.3 doesn't have the
.scalars
method whereas 1.4 does.