[news.eclipse.rt.eclipselink] Re: Dynamic fetch plan with navigations

[fs5@xxxxxxx (Frank Schwarz)]

James, thank you for this hint.

> JPQL: "Select e from Employee e"
> Hint: "eclipselink.join-fetch"="e.manager.phoneNumbers"

I tried it, however it did not take effect in my case. I suppose that 
cascading 1-n-relationships are not supported, i.e. 
"e.subordinates.phoneNumbers".


> I think an option to force instantiation would be useful without requiring 
> joining (such as using batch reading), so feel free to add an enhancement 
> request.  You can also add one for nested fetch groups if you wish.

It is quite hard for me to come up with a enhancement request for fetch 
groups. I mean, the JDO2 expert group accepted this challenge but created 
something with only academic relevance (to say the least). On the other 
hand, the JPA expert group seams to be reluctant to standardize fetch 
groups at all. Maybe the eagerly awaited Criteria query API will include 
something of relevance.

-- Frank