You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if this should be added (as an option or even as a default) to eclipse store itself?
The example given states:
If you e.g. change the address of a person, the changed address is already in your data model, even before storing this person. This is very different from the behavior a Spring user expects.
So, what this means is that in case another user loads the person who's address has just been changed but not yet saved sees the new address already? I wonder who ever would want this behaviour at all.
The xdev working copies approach is available only for spring boot.
Additionally it is somehow confusing to me to have a Spring integration from eclipse store and additionally one from xdev.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Spring-Data-Eclipse-Store uses a working copies approach.
I wonder if this should be added (as an option or even as a default) to eclipse store itself?
The example given states:
So, what this means is that in case another user loads the person who's address has just been changed but not yet saved sees the new address already? I wonder who ever would want this behaviour at all.
The xdev working copies approach is available only for spring boot.
Additionally it is somehow confusing to me to have a Spring integration from eclipse store and additionally one from xdev.
Beta Was this translation helpful? Give feedback.
All reactions