Skip to content

Conversation

@alex-kulakov
Copy link
Contributor

Closes #81

  • Extends test of the DirectPersistentAccessor with new cases which show the problem.
  • Changes entity state to Modified if new value has affect on tuple.
  • Additionally checks for key being from correct storage node before apply its values

@AlexUstinov
Copy link
Contributor

Do you have plans porting this to the master?

@alex-kulakov alex-kulakov deleted the setreference-problem branch October 27, 2020 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DirectPersistentAccessor.SetReferenceKey change Tuple but does not register entity as modified

3 participants