Hi,

I'm working with a content management system that is limited in the sense that it does not create proper relationships between tables, i.e. foreign key constraints to primary/unique keys.

Each table has a database id, a content id and a status field which describes if a particular row (i.e. the content) has been deleted. Relationships between tables can be built using the content id and by checking the status of a particular row.

I'm currently trying to build a parent/child relationship using the "where" attribute on the class and set elements. I'm also using the "property-ref" attribute to build the key for my set of children.

Can anyone advise me if I am heading along the right track?

Also when i set the fetch="join" i seem to get duplicate elements (equal to the number of children that exist) when i query for all parents. Setting fetch="select" works but causes two selects to be executed. Is there a way to get the join to work as it seems more efficient?

Hibernate mappings are as follows.

I am a newbie so this post is ment to be an exploratory step rather an answer. It seems to me that this is one of those cases where all the intelligence of parent-child mapping gets in the way. Why not just use regular queries that retrieve into a hibernate populate entity?

SQLQuery query = getHibernateTemplate().getSessionFactory().getCurrentSession().createSQLQuery("select {c.*} from Children as c where c.parent_id=:id and c.status!='DELETED'");
query.addEntity("c", Children.class);
query.setInteger("id", cid);

List results = query.list();

Let me know what you think :)

Marius Seritan

Because its not as cool. Haha.

I guess I'd just prefer it if hibernate could just do everything for me for the following reason:
1. less work for me
2. ability to retrieve everything in a single call

Thanks for the suggestion though. I will probably end up doing it that way anyhow.

I hear you, the cool factor is what attracted me to Hibernate. But sometimes it seems to get in the way. Even the approach above is MUCH nicer than jdbc.

Good luck!

Marius