fetching data :: eager Vs lazy

[satish bodas]

Using JPA ( with underlying provider as Hibernate )
This fetch mode is defined in the association annotation itself

    
@OneToMany(mappedBy="user",cascade=CascadeType.ALL,[B]fetch=FetchType.EAGER[/B])
public Set getAddress() {

This means that in the client that makes use of this code is stuck
The behaviour is fixed .

Istnt that a disadvantage ?
Can I not change it dynamically based on what client wants ?

There very well could be scenarios that for a user A I only have 2-3 records as addresses and for User B I have 100 records as addresses

I want to do a eager load of data for User A and a lazy load for user B .

Thanks ,
~satish

[Mark Spritzler]

Which is why the default is to load lazy. So that only on use case do you say I want that eager. In creating Query objects you can then set the association to eager load. It should always be use case driven and not one default to rule them all.

Mark