Add ignore_saving_historical_record_on_delete flag #736
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add ignore_saving_historical_record_on_delete flag on HistoricalRecord model which ignores saving history when a model is deleted. Fixes performance issue when cascading deletions create a large number of history instances.
Related Issue
Closes #642 and closes #993.
This relates to #717, #858.
Motivation and Context
Deleting a model that causes a lot of cascading deletions is slow since it creates a new history instance for each delete, potentially causing thousands of database queries.
How Has This Been Tested?
Added new unit tests with the flag set to both True/False
Types of changes
Checklist:
make format
command to format my codeAUTHORS.rst
CHANGES.rst