Dears,

I have a 1:n relation between tables A and B, and I added a restriction to B and want to fetch A and B it eagerly, the question would be what happens when I want to navigate from A to B.

Should you only see the data in B that matches the restriction, or should you see all Bs that are related to A?

Thanks alot

If you defined the restriction on the relation,
then by navigating from A you should just see the B's which fits the restriction.

If you defined the restriction on the entity B,
then by navigating from A you should see all associated B's.

That's I believe the things are working, but 'The proof of the pudding is in the eating.'

Dear Expert,

Thank you for your prompt reply.

Could you please give me an example on "defined the restriction on the relation" because I already defining the restriction on the entity B and I get all the associated B's Which I don't rally want to.


Thanks again

Is it possible to do that in the query not in the mapping?

Now I'm confused.
You previously stated that you want to have the restriction feature when you navigate from A to B,
thus is calling a.assB().



What do you mean with 'do that in the query' ?
Do you intend to do supply a user-query (HQL, Criteria) and with it's result-set initialize the persistent collection which represents the A-B relation ?

Yes, that is what I am trying to do.
I just want to get B that matches the restriction in the user-query when I navigate from A to B "not all associated B's"

Thank you a lot your support.

I don't know if this is actually feasible, I fear not.

Thanks a lot for your help :)