SQLAlchemy Migration Guides
Resolve Engine.execute attribute errors without guessing transaction behavior.
Start here
Use engine.connect() or engine.begin(), then execute on the returned Connection. Do not blindly replace engine.execute with session.execute.
Stop before automation when: Choosing connect() versus begin(). Implicit autocommit replacements.
with engine.connect() as conn:
result = conn.execute(stmt)
with engine.begin() as conn:
conn.execute(user_table.insert(), {"name": "Ada"})
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
Engine.execute was removed, so the replacement depends on whether the code is reading, writing, or wrapping another library.
Direct answer
Use engine.connect() or engine.begin(), then execute on the returned Connection. Do not blindly replace engine.execute with session.execute.
Example
result = engine.execute(stmt)
engine.execute(user_table.insert(), {"name": "Ada"})
with engine.connect() as conn:
result = conn.execute(stmt)
with engine.begin() as conn:
conn.execute(user_table.insert(), {"name": "Ada"})
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 engine.connect() or engine.begin(), then execute on the returned Connection. Do not blindly replace engine.execute with session.execute.
Automate only the supported subset: Detection of removed engine.execute calls. Separation of read and write examples. Fail-closed reporting when transaction semantics are unclear. Keep these cases in manual review: Choosing connect() versus begin(). Implicit autocommit replacements. Helper APIs that hide the engine object.
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