Add a column to internal and external tables (singleauditchecklist, singleauditreportfile, dissemination_*) to contain a hash of the rows data. For now, it will remain internal until a future ticket has us presenting hashes to users.
This work is largely completed by #5246. We should bring it up to date and verify its functions. New tables (dissemination_resubmission) will need to be added. We should perhaps explore using generated fields, or otherwise automatically determine which fields get hashed. That could save us some headaches in the future.
Acceptance Criteria
- Internal and external tables have "hash" columns
- Hashes are updated when the row data changes
a. For in progress submissions, this is all the time
b. For cases of redissemination, this is only when the record is actually effected. Which is almost never. A resubmission may have invoked the change, and it should then only change the hash for the applicable dissemination_resubmission row(s).
Add a column to internal and external tables (
singleauditchecklist,singleauditreportfile,dissemination_*) to contain a hash of the rows data. For now, it will remain internal until a future ticket has us presenting hashes to users.This work is largely completed by #5246. We should bring it up to date and verify its functions. New tables (
dissemination_resubmission) will need to be added. We should perhaps explore using generated fields, or otherwise automatically determine which fields get hashed. That could save us some headaches in the future.Acceptance Criteria
a. For in progress submissions, this is all the time
b. For cases of redissemination, this is only when the record is actually effected. Which is almost never. A resubmission may have invoked the change, and it should then only change the hash for the applicable
dissemination_resubmissionrow(s).