Zipper Tools

SQLAlchemy Migration Guides

How to replace session.query(...).get(...) in SQLAlchemy 2.0

Fix Query.get migrations and move identity lookups onto Session.get(...).

Start here

The safe first move

If the call is a direct primary-key lookup, the mechanical replacement is Session.get(Model, primary_key).

Stop before automation when: Non-trivial Query chains before .get(...). Helper wrappers that hide the session object.

Target shape

user = session.get(User, user_id)
job = db_session.get(Job, job_id)

Repo fit check

Want to know if your repo has this pattern?

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.

  • Local scan; no repository upload.
  • Supported findings are separated from manual-review findings.
  • Buy only when the repeated pattern is worth automating.
Run the SQLAlchemy scan first View example report See when to buy 
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewable

Why this page exists

How to replace session.query(...).get(...) in SQLAlchemy 2.0

This is one of the clearest SQLAlchemy 2.0 migrations and a strong codemod target.

Direct answer

What changes

If the call is a direct primary-key lookup, the mechanical replacement is Session.get(Model, primary_key).

Example

Before and after

Before

user = session.query(User).get(user_id)
job = db_session.query(Job).get(job_id)

After

user = session.get(User, user_id)
job = db_session.get(Job, job_id)

Decision path

If this repeats across the repo, open the evaluation pages next.

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.

  • The free scan shows repeated Query.get, select([..]), string join, string loader, declarative import, or DML constructor findings.
  • The remaining supported cleanup is still expensive enough to justify a controlled local migration workflow.
  • If the scan output is ambiguous, review its findings and upstream guidance. Do not buy expecting unsupported cases to be resolved.

Typical symptoms

  • Legacy Query.get(...) calls still show up in real repos.
  • Teams want the easy 2.0 fixes first.
  • Reviewers do not want to hand-edit dozens of lookup calls.

What the product covers

  • Direct session.query(Model).get(pk) rewrites.
  • Repo reporting for where the pattern appears.
  • A scanner-first qualification path.

Manual-review boundary

  • Non-trivial Query chains before .get(...).
  • Helper wrappers that hide the session object.
  • Calls that are not direct primary-key lookups.

FAQ

Fast answers before you decide

What is the safest fix for session.query get sqlalchemy 2.0?

If the call is a direct primary-key lookup, the mechanical replacement is Session.get(Model, primary_key).

Can session.query get sqlalchemy 2.0 be automated?

Automate only the supported subset: Direct session.query(Model).get(pk) rewrites. Repo reporting for where the pattern appears. A scanner-first qualification path. Keep these cases in manual review: Non-trivial Query chains before .get(...). Helper wrappers that hide the session object. Calls that are not direct primary-key lookups.

When should I buy SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack?

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

Choose the lowest-risk next step.

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.

Buy if

  • The free scan shows repeated Query.get, select([..]), string join, string loader, declarative import, or DML constructor findings.
  • The remaining supported cleanup is still expensive enough to justify a controlled local migration workflow.
  • The team can run the migration on a branch and validate locally before merge.

What the workflow includes

  • Installable local CLI workflow, not a hosted black box.
  • Preview/apply modes, diff output, and JSON migration report.
  • Coverage notes, rollback checklist, manager summary, and buyer terms.

Before checkout

  • Stripe Checkout handles secure payment and receipts.
  • Download your purchased ZIP after payment.
  • Runs locally; no hosted API, repo upload, or production credentials needed.
  • The free report includes the evidence needed to evaluate fit. Paid summary and template add-ons are optional.
  • 14-day refund review for published-scope or delivery mismatches.
Run the SQLAlchemy scan first

Explore the details