Skip to content

Comments

Fix SQLAlchemy 2.x subquery deprecation warnings in controllers#1030

Open
DhanushVarma-2 wants to merge 1 commit intoCCExtractor:masterfrom
DhanushVarma-2:fix/sqlalchemy-subquery-warnings
Open

Fix SQLAlchemy 2.x subquery deprecation warnings in controllers#1030
DhanushVarma-2 wants to merge 1 commit intoCCExtractor:masterfrom
DhanushVarma-2:fix/sqlalchemy-subquery-warnings

Conversation

@DhanushVarma-2
Copy link

@DhanushVarma-2 DhanushVarma-2 commented Feb 21, 2026

Please prefix your pull request with one of the following: [FEATURE] [FIX] [IMPROVEMENT].

In raising this pull request, I confirm the following (please check boxes):

  • I have read and understood the contributors guide.
  • I have checked that another pull request for this purpose does not exist.
  • I have considered, and confirmed that this submission will be valuable to others.
  • I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
  • I give this submission freely, and claim no ownership to its content.

My familiarity with the project is as follows (check one):

  • I have never used the project.
  • I have used the project briefly.
  • I have used the project extensively, but have not contributed previously.
  • I am an active contributor to the project.

{pull request content here}
Several controllers were passing SQLAlchemy Subquery objects directly to .in_(), which triggers a deprecation warning in SQLAlchemy 2.x. This fix explicitly calls .select() on the subquery before passing it to .in_() across mod_sample, mod_test, mod_ci, and mod_customized. All 416 tests pass after the fix. I am still working on it

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant