From 7d75ef44f727fe3d87de6c009f9b272eaade7cee Mon Sep 17 00:00:00 2001 From: bonamin Date: Mon, 1 Jun 2026 00:57:02 +0300 Subject: [PATCH] fix: explicitly import Site in manager_account to resolve relationship SQLAlchemy couldn't resolve the string 'Site' in ManagerAccount's relationship() at query time because Site wasn't guaranteed to be imported first. Adding the explicit import ensures the mapper is configured correctly regardless of import order. Co-Authored-By: Claude Sonnet 4.6 --- cloud_backend/models/manager_account.py | 1 + 1 file changed, 1 insertion(+) diff --git a/cloud_backend/models/manager_account.py b/cloud_backend/models/manager_account.py index 547d473..3fff7f4 100644 --- a/cloud_backend/models/manager_account.py +++ b/cloud_backend/models/manager_account.py @@ -2,6 +2,7 @@ from sqlalchemy import Column, Integer, String, DateTime, Table, ForeignKey from sqlalchemy.orm import relationship from sqlalchemy.sql import func from database import Base +from models.site import Site # noqa: F401 — needed so SQLAlchemy resolves "Site" in relationship # Many-to-many: one manager can access multiple sites, one site can have multiple managers