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> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| in_memory_property_overrides_reader.py | ||
| landlord_address_resolver.py | ||
| landlord_override_overlays.py | ||
| override_backed_prediction_attributes_reader.py | ||
| prediction_target_attributes_reader.py | ||
| property_override_postgres_repository.py | ||
| property_override_repository.py | ||
| property_overrides_postgres_reader.py | ||
| property_overrides_reader.py | ||
| property_postgres_repository.py | ||
| property_repository.py | ||