mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-07-27 23:35:01 +00:00
f7328f54c5
An epc_property row can carry a null property_id (FE/historic ingestion persists EPC rows never linked to a property row), so a property_id-keyed read silently misses them. UPRN is the durable key both the property row and the epc_property row share. Repoint the lodged reads (get_for_property + get_for_properties) onto UPRN; the predicted reads stay on property_id because a predicted EPC deep-copies a neighbour's UPRN, so its UPRN column is never the property's own. UPRN is not unique on epc_property, so the read tie-break is now load- bearing (it was dormant under property_id, where the write path guarantees one lodged row per property): the most recently ingested (highest-id) row wins. Write path stays keyed on (property_id, source). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bulk_upload | ||
| comparable_properties | ||
| epc | ||
| fuel_rates | ||
| geospatial | ||
| historic_epc | ||
| hubspot_deals | ||
| landlord_overrides | ||
| magic_plan | ||
| materials | ||
| plan | ||
| product | ||
| property | ||
| property_baseline | ||
| scenario | ||
| solar | ||
| spatial | ||
| tasks | ||
| unstandardised_address | ||
| uploaded_file | ||
| __init__.py | ||
| postgres_unit_of_work.py | ||
| unit_of_work.py | ||