Skip to content

Bug: postgresql.UUID remains in 9 autobot-backend/models/ files alongside JSONB #2563

@mrveiss

Description

@mrveiss

Problem

PRs #2532 and #2551 replaced postgresql.UUID with sqlalchemy.types.Uuid in 11 model files. However, 9 more files in autobot-backend/models/ still import UUID from sqlalchemy.dialects.postgresql alongside JSONB:

  • autobot-backend/models/process_run.py
  • autobot-backend/models/workflow_audit.py
  • autobot-backend/models/session_collaboration.py
  • autobot-backend/models/activities.py
  • autobot-backend/models/heartbeat.py
  • autobot-backend/models/task_delegation.py
  • autobot-backend/models/config_revision.py
  • autobot-backend/models/approval.py
  • autobot-backend/models/secret.py

These files need the same import-splitting treatment as #2533: keep JSONB from postgresql, move UUID to sqlalchemy.types.Uuid.

Discovered During

Code review of PR #2551 (#2533)

Fix

Apply the same pattern: split from sqlalchemy.dialects.postgresql import JSONB, UUID into two imports, replacing UUID with from sqlalchemy.types import Uuid.

Impact

Breaks SQLite dev/test environments. Medium priority — same as #2495 and #2533.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions