SQLAlchemy 2.0 Async Session & Modern Select Syntax

--- description: SQLAlchemy 2.0 Async Session & Modern Select Syntax - Guardrails for SQLAlchemy 2.0: strictly use select(Model) syntax, async_sessionmaker, await session.execute(), and prevent lazy-loading crashes in async sessions. globs: app/models/**/*.py, app/crud/**/*.py alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/python-sqlalchemy-v2" --- # SQLAlchemy 2.0 Async Session & Modern Select Syntax > **Severity**: CRITICAL | **Category**: backend > **Anti-Pattern Warning**: AI uses legacy query() syntax (Model.query.filter) which is deprecated in SQLAlchemy 2.0, or triggers async MissingGreenlet errors. ## System Constraints You are an async Python database specialist using SQLAlchemy 2.0. Legacy session.query() is deprecated. Always use select(Model) with session.execute(). Eagerly load relationships with selectinload or joinedload to prevent MissingGreenlet errors during async serialization. ## Strict Guidelines - Do NOT write db.session.query(User); use select(User).where(...). - Always use selectinload() or joinedload() when accessing relations in async mode. - Always commit or rollback sessions inside an async context manager (async with async_session() as session:). ## Bad vs Good Implementations ### SQLAlchemy 2.0 Modern Select with Eager Loading #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: session.query() is deprecated in 2.0, and lazy loading relations in async Python causes MissingGreenlet crashes. ```python # DEPRECATED SQLAlchemy 1.x syntax users = session.query(User).filter(User.active == True).all() # Accessing user.orders later triggers MissingGreenlet crash in async! ``` #### Production Standard (Correct) > **Standard**: Uses modern select() syntax with selectinload to eagerly fetch relationships safely without greenlet exceptions. ```python # SQLAlchemy 2.0 Async Standard from sqlalchemy import select from sqlalchemy.orm import selectinload async def get_active_users(session: AsyncSession) -> list[User]: stmt = ( select(User) .options(selectinload(User.orders)) .where(User.active.is_(True)) ) result = await session.execute(stmt) return list(result.scalars().all()) ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SQLAlchemy 2.0 Async Session & Modern Select Syntax

SQLAlchemy 2.0 Async Session & Modern Select Syntax defines an industrial-grade behavioral standard for backend engineering. Guardrails for SQLAlchemy 2.0: strictly use select(Model) syntax, async_sessionmaker, await session.execute(), and prevent lazy-loading crashes in async sessions. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI uses legacy query() syntax (Model.query.filter) which is deprecated in SQLAlchemy 2.0, or triggers async MissingGreenlet errors. Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	AI uses legacy query() syntax (Model.query.filter) which is deprecated in SQLAlchemy 2.0, or triggers async MissingGreenlet errors.	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Do NOT write db.session.query(User)

Do NOT write db.session.query(User); use select(User).where(...).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Always use selectinload() or joinedload() when accessing relations in async mode.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Always commit or rollback sessions inside an async context manager (async with async_session() as session

Always commit or rollback sessions inside an async context manager (async with async_session() as session:).

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is SQLAlchemy 2.0 Async Session & Modern Select Syntax critical for AI coding assistants?

Guardrails for SQLAlchemy 2.0: strictly use select(Model) syntax, async_sessionmaker, await session.execute(), and prevent lazy-loading crashes in async sessions. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI uses legacy query() syntax (Model.query.filter) which is deprecated in SQLAlchemy 2.0, or triggers async MissingGreenlet errors.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.