feat: Implement update_level_offset in RelationalBone#1432
Draft
sveneberth wants to merge 3 commits into
Draft
Conversation
…#1430) This function is used rarely, and it makes sense to always obtain a sorted list of skeletons. As the function now also returns a list, it can be directly returned as sorted. This affects, for example, callable tasks which provide a kind selector, like RebuildSearchIndex.
To be honest, I don't (yet) have a concrete use case. But to increase the efficiency of the relational system and reduce write ops, this feature came to my mind. I still have to test it. so far I've only implemented it down like this. Please share your opinions and thoughts.
sveneberth
added
feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
To be honest, I don't (yet) have a concrete use case. But to increase the efficiency of the relational system and reduce write ops, this feature came to my mind.
I still have to test it. so far I've only implemented it down like this. Please share your opinions and thoughts.
This PR might solve #117 if you set the offset to a big value