The best I could come up
with is that we do it for auditing purposes.
correct. auditing is a major reason
I wanted to get some feedback on this for a couple reasons. First,
it
will help provide some better context for a bug I working on. Secondly,
if these changes are feasible, we might be able to simplify some code
where InventoryStatus.DELETED is currently used, and we will be able to
provide more robust audit trails.
What is the alternative to a hard foreign key relationship to Resource?
without that, alot of changes to the code would be necessary.