chore(db): resolve SQLAlchemy scalar_subquery deprecation warnings#1052
Merged
canihavesomecoffee merged 2 commits intoCCExtractor:masterfrom Mar 12, 2026
Merged
Conversation
MrButtCode
requested review from
canihavesomecoffee and
thealphadollar
as code owners
canihavesomecoffee
requested changes
Mar 8, 2026
canihavesomecoffee
approved these changes
Mar 12, 2026
canihavesomecoffee
force-pushed
the
chore/db-deprecation-warnings
branch
from
7953ef8 to
9c74f52
Compare
|
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
2 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.
Resolves multiple
SAWarningdeprecation warnings generated by SQLAlchemy during the test suite execution.In newer versions of SQLAlchemy, coercing a
Subqueryobject into aselect()for use in anIN()clause throws a deprecation warning: "SAWarning: Coercing Subquery object into a select() for use in IN(); please pass a select() construct explicitly".To resolve this and modernize the database queries, I updated the
.subquery()calls to.scalar_subquery()acrossmod_ci,mod_customized,mod_sample, andmod_testwhere they are explicitly used inside.in_()filters. This eliminates the warnings during the test run and ensures future compatibility with SQLAlchemy 2.0 paradigms.