Having multiple navigation properties to the same table results in incorrect EntityState for second property's children about detached-mapper HOT 7 CLOSED

Thanks! I'll fix it asap.

from detached-mapper.

I've added an unnecesary cycle check in LoadAsync (GetIncludePaths).
It's fixed in version 1.1.1, please check and let me know.
Just make sure you don't add [Owned] or [Associated] to a back reference navigation property (the one that points to the parent).

from detached-mapper.

I think the problem is that during UpdateAsync it is not loading the entire object graph from the database for A to compare with the detached object graph, resulting in an incomplete comparison. This would mean that when gettings B2 from the database it does not load B2.C from the DB.

from detached-mapper.

I just tested the same scenario for LoadAsync and it is the same. It will load A.B1.C but will not load A.B2.C.

from detached-mapper.

And sorry for the delay! I had a lot of work from my job.

from detached-mapper.

it seems ok now, thanks for the quick response.

from detached-mapper.

from detached-mapper.