Implement document change tracking #521
Closed
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.
Add a series of hooks to the session to monitor the update of the document object and implement actions after the document changes.
Such as implementing dynamic indexing, which seems to be difficult with the current design of Yessql.
In OC, neither ContentHandler nor a fake IndexProvider can determine whether an object needs to be saved to the database immediately. So the custom dynamic indexing functionality can only be written to the database immediately each time
Through these hooks, we can insert custom code into the
_commands
list of the Session to achieve free insertion when the document is updatedrelate:
#505