(ORM Support Classes version 1.0.20051.060425)
This is actually not a problem, as we determined that what we were trying to do was not done purposely (so really a bug in our code). Still, the result was unexpected.
I can email DDL/code if required, but since it might be a known behavior, I thought I would post the general question here first.
Basically we were doing a prefetch path that involved a 1:1 relationship between X and Y. X was actually a subpath of another entity BASE with which it also has a 1:1 relationship.
The fetch went BASE (the base entity of the prefetch) =>
subpath X1 =>
subpath Y =>
subpath X2
(1 and 2 added for clarity)
So you would expect that you could access BASE.X1.Y.X2.
The odd thing was, both Y and X2 came back as null, even though the data was there to support them. In addition, when I ran this fetch with the profiler running, all queries returned the correct data.
Is this expected behavior?