Entity creation: improved speed (avoid validating sibling keys when not necessary) #256
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 fix uses the node "flags" (created/updated/deleted) used by Arena (desktop) to update the RDB.
In multiple entities with key, when a new entity is added, some key nodes should be re-validated (they could be duplicate). There are 2 cases:
When a key attribute is updated, key nodes with the same value or key nodes with errors (they could be already marked as duplicate) should be re-validated.
Once an entity is created or a node updated, all updated nodes flags should be removed (outside of RecordUpdater function call invocation).