Re: Assertion A14.6-21 (Query.getFetchPlan)

2005-10-26 Thread Craig L Russell
Hi Michael, Craig On Oct 25, 2005, at 5:55 AM, Michael Watzek wrote: Hi Craig, Hi Michael, The relevant bit of the specification is regarding jdoPostLoad. A10.1-2 [This method is not modified by the enhancer.] So whatever is done in jdoPostLoad, the implementation will not be called

Re: Assertion A14.6-21 (Query.getFetchPlan)

2005-10-25 Thread Michael Watzek
Hi Craig, Hi Michael, The relevant bit of the specification is regarding jdoPostLoad. A10.1-2 [This method is not modified by the enhancer.] So whatever is done in jdoPostLoad, the implementation will not be called transparently. But the spec doesn't require jdoPostLoad to be called if

Assertion A14.6-21 (Query.getFetchPlan)

2005-10-20 Thread Michael Watzek
Hi, assertion A14.6-21 specifies: This method retrieves the fetch plan associated with the Query. It always returns the identical instance for the same Query instance. Any change made to the fetch plan affects subsequent query execution. I wonder, how the second part of this assertion can

Re: Assertion A14.6-21 (Query.getFetchPlan)

2005-10-20 Thread Michael Bouschen
Hi Michael, this is a good question and I'm not sure whether I have a good answer :-). The post-load attribute defaults to true for the default-fetch-group. So I'm wondering whether you are able to see any difference, if you remove the default-fetch-group and add a new fetch group having the

Re: Assertion A14.6-21 (Query.getFetchPlan)

2005-10-20 Thread Craig L Russell
Hi Michael, The relevant bit of the specification is regarding jdoPostLoad. A10.1-2 [This method is not modified by the enhancer.] So whatever is done in jdoPostLoad, the implementation will not be called transparently. But the spec doesn't require jdoPostLoad to be called if only fetch