-
Notifications
You must be signed in to change notification settings - Fork 31
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
Towards compatibility with SQLAlchemy 2.x #485
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
be101e8
Tests/Chore: Properly close socket connections to silence warnings
amotl 85d6273
CI/Sandbox: Update to SQLAlchemy 1.4.45 and CrateDB 5.1.2
amotl 055030c
SA20: Run tests with `SQLALCHEMY_WARN_20=1`
amotl 13de09f
SA20: Towards compatibility with SQLAlchemy 2.x
amotl a553233
SA20: Address deprecation warnings in SqlAlchemyDictTypeTest
hammerhead ddfee8a
SA20: Fix SqlAlchemyDictTypeTest
amotl b4ade5c
Revert "SA20: Address deprecation warnings in SqlAlchemyDictTypeTest"
amotl c1dc310
SA20: Fix SqlAlchemyDictTypeTest
amotl b5237cf
SA20: Fix SqlAlchemyInsertFromSelectTest
amotl 10eb284
CI: Turn off "fail-fast" on the test matrix to get the big picture
amotl 5bff9d2
SA20: Restore backward-compatibility with SQLAlchemy 1.3
amotl 19dbf7d
SA20: Restore backward-compatibility with SQLAlchemy 1.3
amotl 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 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 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 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 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 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 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 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 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
Empty file.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,133 @@ | ||
# -*- coding: utf-8; -*- | ||
# | ||
# Licensed to CRATE Technology GmbH ("Crate") under one or more contributor | ||
# license agreements. See the NOTICE file distributed with this work for | ||
# additional information regarding copyright ownership. Crate licenses | ||
# this file to you under the Apache License, Version 2.0 (the "License"); | ||
# you may not use this file except in compliance with the License. You may | ||
# obtain a copy of the License at | ||
# | ||
# https://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT | ||
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the | ||
# License for the specific language governing permissions and limitations | ||
# under the License. | ||
# | ||
# However, if you have executed another commercial license agreement | ||
# with Crate these terms will supersede the license and you may use the | ||
# software solely pursuant to the terms of the relevant commercial agreement. | ||
|
||
""" | ||
Compatibility module for running a subset of SQLAlchemy 2.0 programs on | ||
SQLAlchemy 1.3. By using monkey-patching, it can do two things: | ||
1. Add the `exec_driver_sql` method to SA's `Connection` and `Engine`. | ||
2. Amend the `sql.select` function to accept the calling semantics of | ||
the modern variant. | ||
Reason: `exec_driver_sql` gets used within the CrateDB dialect already, | ||
and the new calling semantics of `sql.select` already get used within | ||
many of the test cases already. Please note that the patch for | ||
`sql.select` is only applied when running the test suite. | ||
""" | ||
|
||
import collections.abc as collections_abc | ||
|
||
from sqlalchemy import exc | ||
from sqlalchemy.sql import Select | ||
from sqlalchemy.sql import select as original_select | ||
from sqlalchemy.util import immutabledict | ||
|
||
|
||
# `_distill_params_20` copied from SA14's `sqlalchemy.engine.{base,util}`. | ||
_no_tuple = () | ||
_no_kw = immutabledict() | ||
|
||
|
||
def _distill_params_20(params): | ||
if params is None: | ||
return _no_tuple, _no_kw | ||
elif isinstance(params, list): | ||
# collections_abc.MutableSequence): # avoid abc.__instancecheck__ | ||
if params and not isinstance(params[0], (collections_abc.Mapping, tuple)): | ||
raise exc.ArgumentError( | ||
"List argument must consist only of tuples or dictionaries" | ||
) | ||
|
||
return (params,), _no_kw | ||
elif isinstance( | ||
params, | ||
(tuple, dict, immutabledict), | ||
# only do abc.__instancecheck__ for Mapping after we've checked | ||
# for plain dictionaries and would otherwise raise | ||
) or isinstance(params, collections_abc.Mapping): | ||
return (params,), _no_kw | ||
else: | ||
raise exc.ArgumentError("mapping or sequence expected for parameters") | ||
|
||
|
||
def exec_driver_sql(self, statement, parameters=None, execution_options=None): | ||
""" | ||
Adapter for `exec_driver_sql`, which is available since SA14, for SA13. | ||
""" | ||
if execution_options is not None: | ||
raise ValueError( | ||
"SA13 backward-compatibility: " | ||
"`exec_driver_sql` does not support `execution_options`" | ||
) | ||
args_10style, kwargs_10style = _distill_params_20(parameters) | ||
return self.execute(statement, *args_10style, **kwargs_10style) | ||
|
||
|
||
def monkeypatch_add_exec_driver_sql(): | ||
""" | ||
Transparently add SA14's `exec_driver_sql()` method to SA13. | ||
AttributeError: 'Connection' object has no attribute 'exec_driver_sql' | ||
AttributeError: 'Engine' object has no attribute 'exec_driver_sql' | ||
""" | ||
from sqlalchemy.engine.base import Connection, Engine | ||
|
||
# Add `exec_driver_sql` method to SA's `Connection` and `Engine` classes. | ||
Connection.exec_driver_sql = exec_driver_sql | ||
Engine.exec_driver_sql = exec_driver_sql | ||
|
||
|
||
def select_sa14(*columns, **kw) -> Select: | ||
""" | ||
Adapt SA14/SA20's calling semantics of `sql.select()` to SA13. | ||
With SA20, `select()` no longer accepts varied constructor arguments, only | ||
the "generative" style of `select()` will be supported. The list of columns | ||
/ tables to select from should be passed positionally. | ||
Derived from https://github.com/sqlalchemy/alembic/blob/b1fad6b6/alembic/util/sqla_compat.py#L557-L558 | ||
sqlalchemy.exc.ArgumentError: columns argument to select() must be a Python list or other iterable | ||
""" | ||
if isinstance(columns, tuple) and isinstance(columns[0], list): | ||
if "whereclause" in kw: | ||
raise ValueError( | ||
"SA13 backward-compatibility: " | ||
"`whereclause` is both in kwargs and columns tuple" | ||
) | ||
columns, whereclause = columns | ||
kw["whereclause"] = whereclause | ||
return original_select(columns, **kw) | ||
|
||
|
||
def monkeypatch_amend_select_sa14(): | ||
""" | ||
Make SA13's `sql.select()` transparently accept calling semantics of SA14 | ||
and SA20, by swapping in the newer variant of `select_sa14()`. | ||
This supports the test suite of `crate-python`, because it already uses the | ||
modern calling semantics. | ||
""" | ||
import sqlalchemy | ||
|
||
sqlalchemy.select = select_sa14 | ||
sqlalchemy.sql.select = select_sa14 | ||
sqlalchemy.sql.expression.select = select_sa14 |
Oops, something went wrong.
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.
Do we already know how much longer we intend to support SQLAlchemy 1.3? According to SQLAlchemy's version policy, 1.3 will become EOL as soon as 2.0 becomes stable. Given that maintaining compatibility with 1.3 here reaches a certain complexity, do we want to keep it much longer?
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.
Hi. The most recent discussion about EOL of SA13 can be found at sqlalchemy/sqlalchemy#8631 (comment). I think we will support it for a while, and I am happy that the changes have not been too much intrusive, other than needing a few lines in
compat/api13.py
.We discussed different alternatives on maintenance of the code within this package with @seut, regarding version deprecations and such, but all other alternatives would need more efforts, especially if we would need to deprecate support for SA13 earlier, because this might mean we would have to keep a maintenance branch or such. See also GH-494.
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.
Nevertheless, I think it will not hurt to add a runtime warning for the next release, which will give users a notice that dropping support for SA13 will be around the corner.
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.
The 1.3 support is quite nicely encapsulated, indeed. Well done! For now (while 1.3 is still supported upstream) it's a good solution. Once 1.3 reached EOL, I would still vote for removing it shortly after to eliminate the need for monkey patching (which always feels a bit risky to me, especially in tests).
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.
+1 for removing 1.3 support. Given that crate-python is mostly stable (bugfixes are rare) we can point users of SQLAlchemy 1.3 to an older version of crate-python and make sure to update the version constraints for the next crate-python release.
pip
should then pick the right version, no?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.
I agree. See also GH-501.