mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-06-08 11:17:27 +00:00
01c2c3910e
Standardise the modelling persistence classes on the …Model suffix (PlanModel, RecommendationModel, RecommendationMaterialModel) — matching the epc_property precedent and the legacy names the rest of backend/ already imports, so the shim's plan re-export becomes literal (no alias) and the eventual shim deletion needs zero renames. The …Row→…Model sweep for the non-cluster tables (Property/Task/Material/…) waits until their live legacy …Model counterparts are retired, to avoid reintroducing dual-definition collisions. No behaviour change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
22 lines
743 B
Python
22 lines
743 B
Python
"""SQLModel definitions of the Modelling stage's live persistence tables
|
|
(ADR-0017 amendment).
|
|
|
|
One canonical SQLModel per physical table — `plan`, `recommendation`,
|
|
`recommendation_materials` — replacing the legacy SQLAlchemy `Base` models in
|
|
`backend/app/db/models/recommendations.py` (now a re-export shim, the
|
|
`epc_property` pattern). `recommendation` carries `plan_id`; the
|
|
`plan_recommendations` m2m is retired.
|
|
"""
|
|
|
|
from infrastructure.postgres.modelling.plan_table import PlanModel, PlanType
|
|
from infrastructure.postgres.modelling.recommendation_table import (
|
|
RecommendationMaterialModel,
|
|
RecommendationModel,
|
|
)
|
|
|
|
__all__ = [
|
|
"PlanModel",
|
|
"PlanType",
|
|
"RecommendationModel",
|
|
"RecommendationMaterialModel",
|
|
]
|