Use smw_rev field to check if update is skippable, refs 2365, 3390 #3712
Conversation
This file contains 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
mwjames
added a commit
that referenced
this pull request
Feb 23, 2019
… to detect "skippable", refs #3712 [skip ci]
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is made in reference to: #2365, #3390
This PR addresses or contains:
smw_revfield to track associated revision #3390 we have an associate revision field, so instead of using the cache to temporary store which update belongs to which revision (to avoid duplicates updates when refreshlinks runsLinksUpdateasEnqueueableDataUpdate, see Track persistent update marker (MW 1.29+) #2365) use thesmw_revto probe whether the update is skippable or not due to SMW already knowing the revision.This PR includes: