SQLAlchemy Migration Guides
Replace joinedload("addresses") and similar string loader options with mapped attributes when the relationship root is obvious.
Start here
For straightforward paths, replace the string with the mapped attribute, like joinedload(User.addresses).
Stop before automation when: Dotted paths like joinedload("orders.items"). contains_eager and duplicate-join interactions.
query = session.query(User).options(joinedload(User.addresses))
query = query.options(selectinload(User.orders))
Repo fit check
Run the matching scanner locally first. Read the free findings and manual alternatives; consider paid cleanup only if supported patterns repeat enough to justify the price.
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewableWhy this page exists
Simple loader strings are cleanup work. Dotted paths and query-shape-dependent options are not.
Direct answer
For straightforward paths, replace the string with the mapped attribute, like joinedload(User.addresses).
Example
query = session.query(User).options(joinedload("addresses"))
query = query.options(selectinload("orders"))
query = session.query(User).options(joinedload(User.addresses))
query = query.options(selectinload(User.orders))
Decision path
Start with the free scan, inspect the report, and only move to the cleanup pack if the repo has repeated supported patterns that are still expensive to fix by hand.
Before checkout
Price: $299.99 per team.
Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.
FAQ
For straightforward paths, replace the string with the mapped attribute, like joinedload(User.addresses).
Automate only the supported subset: Simple joinedload/lazyload/selectinload/subqueryload string cleanup. Mapped-attribute replacements when the root entity is obvious. Cross-links to the dotted-path and joinedload_all manual buckets. Keep these cases in manual review: Dotted paths like joinedload("orders.items"). contains_eager and duplicate-join interactions. Cases where the owning entity is not obvious from the local code.
Use SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Use the free report and upstream guide to evaluate fit. Buy only if repeated supported edits justify the price; no paid assessment is required.
Purchase fit
One matching page is not enough by itself. Run the local scan, then buy only when the same supported pattern appears often enough to matter.
Replace session.query(...).get(...), Session.query migration guide, Fix engine.execute(...) removal, Clean up joinedload_all(...), Fix select([..]) list syntax, Replace string join paths, Move sqlalchemy.ext.declarative imports to sqlalchemy.orm, Replace insert(..., values=...)
View all SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack guides