Thanks Aaron, your suggestion is working well. It is analogous to a "git
rebase” ;-) I feel better with this code.
I did find that the technique did not work for to-many relationships, but added
a bit of code towards the end of the method to refresh the to-many
relationships using Wonder:
Thanks Aaron that is a great suggestion. I will give that a try as it does not
require messing with snapshots and getting down to lower layers of EOF. I think
I would feel better with an implementation like that.
As for ERXJGroupsSynchronizer, I am not familiar with that and can't really
tell
Dear all,
I’m debugging a deadlock and realise that I probably need to re-design some of
my code logic.
Am I right in saying…
1. For a background thread, it is appropriate to create a new editing context
(ERXEC.newEditingContext(osc)) using a dedicated and new object store
coordinator
Hi all,
I have a need to refresh the to-one relationship of an object, so that if
someone in another app or perhaps in a different EOF stack within the same app
has updated the to-one to point to a different object then I want my EO’s to
one to point to the correct EO. I do not want to
