SQLAlchemy Migration Guides
Fix the common OptionEngine execute error by moving execution onto a Connection or Session.
Start here
Open an explicit connection, wrap raw SQL in text(...), and pass the Connection into code that still expects an executable object.
Stop before automation when: Transaction boundaries around writes. Third-party libraries that need version-compatible adapters.
from sqlalchemy import text
with engine.connect() as conn:
rows = pd.read_sql_query(text("SELECT id FROM users"), conn)
result = conn.execution_options(stream_results=True).execute(stmt)
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 error usually means code or a dependency still expects the removed Engine.execute path.
Direct answer
Open an explicit connection, wrap raw SQL in text(...), and pass the Connection into code that still expects an executable object.
Example
rows = pd.read_sql_query("SELECT id FROM users", engine)
result = engine.execution_options(stream_results=True).execute(stmt)
from sqlalchemy import text
with engine.connect() as conn:
rows = pd.read_sql_query(text("SELECT id FROM users"), conn)
result = conn.execution_options(stream_results=True).execute(stmt)
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
Open an explicit connection, wrap raw SQL in text(...), and pass the Connection into code that still expects an executable object.
Automate only the supported subset: Detection of engine and OptionEngine execution paths. Manual-review reporting for execution-boundary changes. Links to the broader engine.execute removal guide. Keep these cases in manual review: Transaction boundaries around writes. Third-party libraries that need version-compatible adapters. Raw SQL strings that should become text(...).
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, Replace string loader options, Move sqlalchemy.ext.declarative imports to sqlalchemy.orm
View all SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack guides