SQLAlchemy Migration Guides
Replace joinedload_all(...) with mapped-attribute loader options and bucket the hard cases honestly.
Start here
Use joinedload(...) with mapped attributes when the relationship path is obvious. Stop when aliasing or dotted paths make the replacement unclear.
Stop before automation when: Alias-heavy loading. Dotted paths tied to query shape.
query = session.query(User).options(
joinedload(User.orders).joinedload(Order.items)
)
query = query.options(joinedload(User.addresses))
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
joinedload_all(...) is gone. Simple paths are fixable. Ambiguous paths should stay manual.
Direct answer
Use joinedload(...) with mapped attributes when the relationship path is obvious. Stop when aliasing or dotted paths make the replacement unclear.
Example
query = session.query(User).options(joinedload_all("orders.items"))
query = query.options(joinedload_all("addresses"))
query = session.query(User).options(
joinedload(User.orders).joinedload(Order.items)
)
query = query.options(joinedload(User.addresses))
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
Use joinedload(...) with mapped attributes when the relationship path is obvious. Stop when aliasing or dotted paths make the replacement unclear.
Automate only the supported subset: Simple joinedload_all(...) replacements. Cross-links to string loader cleanup pages. Fail-closed reporting when the path is not straightforward. Keep these cases in manual review: Alias-heavy loading. Dotted paths tied to query shape. contains_eager and custom join interactions.
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, Fix select([..]) list syntax, Replace string join paths, Replace string loader options, Move sqlalchemy.ext.declarative imports to sqlalchemy.orm, Replace insert(..., values=...)
View all SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack guides