Hi Lon, I've tried to dig dipper into your case, and I can't repeat described behavior, all I see is that toOne relationship in object that moved to other context is faulted and resolved on next access, and no reverse relationships are affected. And that I assume is expected behavior.
And even more I can't figure out case when line 194 in DataRowUtils can be hit. May be you can provide some simple test case? On Mon, Jul 17, 2017 at 9:14 PM, Lon Varscsak <[email protected]> wrote: > Okay, that didn’t work. > https://www.dropbox.com/s/68hsculni16ucg3/Screen%20Shot%202017-07-13%20at%2010.50.24%20AM.png?dl=0 > > -Lon > > On Mon, Jul 17, 2017 at 11:06 AM, Lon Varscsak <[email protected]> > wrote: > >> Try this: >> >> http://gofile.me/34oeM/YdPU7U4j1 >> >> On Mon, Jul 17, 2017 at 10:08 AM, Andrus Adamchik <[email protected]> >> wrote: >> >>> Unfortunately the mailing list strips attachments. Could you post the >>> image elsewhere, like GoogleDrive or Dropbox? >>> >>> Andrus >>> >>> > On Jul 13, 2017, at 8:51 PM, Lon Varscsak <[email protected]> >>> wrote: >>> > >>> > I found the line that’s nulling it out…I just don’t understand at this >>> deep level what’s going on. Here’s the strack trace: >>> > >>> > On Thu, Jul 13, 2017 at 10:43 AM, Lon Varscsak <[email protected]> >>> wrote: >>> > I have an object (that’s new) in ObjectContextA that has a relationship >>> to another new object (same OC) which also has a reverse relationship. I >>> then create a child of that OC (ObjectContactB) and grab a local version of >>> the first object. At that time, the relationship object (and it’s reverse) >>> is there and all is good in the world. >>> > >>> > The moment I touch the object (setting a simple property with >>> writeProperty) in the relationship the reverse relationship gets nulled >>> out. Any thoughts as to why this might happen? >>> > >>> > -Lon >>> > >>> >>> >> -- Best regards, Nikita Timofeev
