SQLAlchemy Migration Guides
Fix engine.execute removals and OptionEngine errors without pretending the replacement is always trivial.
Start here
Move execution onto a Connection or Session and make transaction boundaries explicit. That is why honest tooling buckets engine.execute(...) as manual review.
Stop before automation when: Choosing Connection versus Session. Raw SQL that needs text(...).
from sqlalchemy import text
with engine.connect() as conn:
result = conn.execute(text("SELECT id FROM users"))
rows = conn.execute(stmt).fetchall()
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
This is a real migration pain point because there is not one safe automatic replacement.
Direct answer
Move execution onto a Connection or Session and make transaction boundaries explicit. That is why honest tooling buckets engine.execute(...) as manual review.
Example
result = engine.execute("SELECT id FROM users")
rows = engine.execute(stmt).fetchall()
from sqlalchemy import text
with engine.connect() as conn:
result = conn.execute(text("SELECT id FROM users"))
rows = conn.execute(stmt).fetchall()
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
Move execution onto a Connection or Session and make transaction boundaries explicit. That is why honest tooling buckets engine.execute(...) as manual review.
Automate only the supported subset: Detection and classification of engine.execute(...) usage. Repo reporting for the manual bucket. Links to related SQLAlchemy guides. Keep these cases in manual review: Choosing Connection versus Session. Raw SQL that needs text(...). Pandas and helper wrappers around execution.
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, Clean up joinedload_all(...), 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