Add support for syncing more complex paths #35
Merged
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.
It is currently difficult to sync on a small portion of a model if that model includes a list element. For example /node1/node2//node3/node4. The current method would be to select node1/node2/ then exclude the unwanted fields. This however can cause substantial processing.
This change allows paths of type /node1/node2/*/node3/node4 to be entered. The new code uses apteryx_query and apteryx_watch_tree to retrieve the database information to synchronize.
Additionally exclude paths are now only applied to the model they were added with.