Support '__all__' in no_db_index to exclude all fields from indexing in the Historical Model #1492
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
Adds support for using
__all__
in theno_db_index
to exclude all fields from being indexed in the historical model.Related Issue
Closes #1491
Motivation and Context
Although fields can be excluded from indexing individually via
no_db_index
, there's currently no simple way to exclude all fields at once. This adds a cleaner approach using'__all__'
.How Has This Been Tested?
Added a unit test to confirm that setting
no_db_index = '__all__'
results in no indexed fields in the historical model.Screenshots (if appropriate):
Types of changes
Checklist:
pre-commit run
command to format and lint.AUTHORS.rst
CHANGES.rst