I have a class:

[code]public class UserAll extends User {

private [b]Employer[/b] employer = null;
private [b]Collection[/b] roles = new LinkedList();
private [b]Collection [/b]groups = new LinkedList();

public UserAll() {
super();
}

public UserAll (long id) {
super(id);
}

/* setters / getters below */[/code]

I have a search screen which has the name, employers, groups and roles that we allow a user to search from. We then dynamically generate the sql, depending on what the user input, to return our UserAll objects.

We are running into a performance issue since Hibernate seems to be running a query for EVERY UserAll objects groups, roles and employers, etc, etc. We've tried using HQL but have had no luck with speeding up the performance.

Does anyone hear have any ideas as to speed this process up?

What was your mapping? Do you map your associations as Lazy? Do you use fetch join in HQL?

Two suggestions
1) Use lazy mappings for your collections if you don't require them in the result
2) If you require these collections Use left join fetch

We're using HQL and we've tried a left outer join to get the Collection of groups. However we need 3 groups of Collections with our UserAll object. According to Hibernate, you can only attach one Collection to an object, which leaves us with an imcomplete object...

Any suggestions?

Our mapping on the userAll object has a lazy fetch

The thing is, we can have to switch lazy=false because we need that object to contain everything, except on this one screen. The screen I am referring to is a user search screen where they can search for a user by their last name, first name, a group they belong to or a role they belong to.

Depending on what the user enters we dynamically create the sql to pull back the information. We're wondering if we could pull all the Collection information into our UserAll object with one simple sql statement instead of Hibernate going to the database for every role, every group, etc, etc. One UserAll Object ends up having to make about 7 queries to populate it.

We've tried using HQL with outer joins and with fetch, however none of these solutions seems to work. It seems as though hibernate only allows us to fetch one Collection into an object at a time, which means hibernate still has to do many queries to populate that Object.

Anyways, I hope this is making sense... any help would be greatly appreciated