I have a process I run every couple months or so that iterates over all versions in our Geodatabase and reports info about those with conflicts. I've always run this with the option to resolve in favor of the parent version (SDE.DEFAULT).
Something recently caught my eye and I tried to reconcile a particular conflict version in favor of the child. This time no conflicts!
Then I ran the whole process and found there to be a couple hundred fewer conflict versions if I choose to resolve in favor of the child. It seems the differences were all with Update-Delete conflicts. That is, where an Update-Delete conflict might appear when resolving in favor of the parent, it *might* not when resolving in favor of the child. (There were still some Update-Delete conflicts even when resolving in favor of the child.)
I'm trying to wrap my head around why this would be the case. On the surface it seems unintuitive.
Thanks for any info you can pass on!
Ed
