Zipper Tools

SQLAlchemy Migration Guides

What to do about Query.from_self() removal in SQLAlchemy 2.0

Treat Query.from_self() as a manual-review migration instead of pretending there is one safe automatic replacement.

Start here

The safe first move

Keep Query.from_self() in manual review. The right replacement depends on the surrounding query structure and what rows should come back.

Stop before automation when: Selecting the right select()/subquery replacement. Result-shape and column-projection decisions.

Target shape

# manual review required
# replacement depends on the surrounding query and result shape

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

What to do about Query.from_self() removal in SQLAlchemy 2.0

from_self() is a real migration problem, but the replacement depends on query shape and result semantics.

Direct answer

What changes

Keep Query.from_self() in manual review. The right replacement depends on the surrounding query structure and what rows should come back.

Example

Before and after

Before

query = session.query(User).filter(User.active == True).from_self(User.id)

After

# manual review required
# replacement depends on the surrounding query and result shape

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

  • Repos still depend on Query.from_self() in legacy ORM code.
  • Teams want an honest stop signal instead of a guessed rewrite.
  • Reviewers need to separate this from the easy Query cleanup bucket.

What the product covers

  • Detection and reporting for Query.from_self() usage.
  • Cross-links to the safe Query.get and string-join cleanup pages.
  • Repo-fit guidance before buying the SQLAlchemy pack.

Manual-review boundary

  • Selecting the right select()/subquery replacement.
  • Result-shape and column-projection decisions.
  • Query chains that already need broader 2.0 redesign.

FAQ

Fast answers before you decide

What is the safest fix for from_self removed sqlalchemy 2.0?

Keep Query.from_self() in manual review. The right replacement depends on the surrounding query structure and what rows should come back.

Can from_self removed sqlalchemy 2.0 be automated?

Automate only the supported subset: Detection and reporting for Query.from_self() usage. Cross-links to the safe Query.get and string-join cleanup pages. Repo-fit guidance before buying the SQLAlchemy pack. Keep these cases in manual review: Selecting the right select()/subquery replacement. Result-shape and column-projection decisions. Query chains that already need broader 2.0 redesign.

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