Referential Integrity for Deletes
# support
t
Is there a way to enforce referential integrity for Delete calls? I'm aware of
checkReferencesOnWrite
, but that seems to only apply for create/update as far as i can tell. For example: - create Patient A - create Encounter 1, references Patient A - Delete Patient A - desired: error due to Encounter 1 referencing patient - current: Patient A is deleted, leaving Encounter 1 dangling
r
HI @tterry_ensomata_25325 , we don't support RI for deletes at this time
Enforcing referential integrity introduces a tradeoff between accuracy and performance. Our current referential integrity only checks outbound references from a resource upon write
Checking inbound reference would require checking all resources in a project for references to the deleted resource
We completely understand the important for mantaining referential integrity upon delete, but unfortunately currently our performance tradeoffs forbid us from implementing this
182 Views