Fix for fetching related information / dynamic immutable_lock_field #1
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.
In my project I've set immutable_lock_field to a @Property, to have a dynamic locking mechanism. Django tries to store some cached relations when computing the immutable_lock_field, but it can't because all changes must be allowed by ImmutableModel. This results in a recursion, so I think ImmutableModel should always allow changing fields starting with
_
, as by Python conventions such variables should be considered private/protected.