I'm teetering on the edge of "to hell with hibernate, I'm using jdbc."

What I'm trying to do is very simple: I have a one-to-many relationship. I need to use eager fetching. The trouble is that the ManyToOne column needs to be part of the primary key for the class in question. I've tried the following approaches:

1) Composite PK class - Result: infinite loop. Apparently a known hibernate bug.

2) Using IdClass to specify a composite primary key including the foreign key. This required adding a second non-updatable property for the foreign key - Result: Index out of bounds exception. Note that this approach was suggested as a workaround for the bug in approach 1.

3) Using IdClass to specify a composite primary key which includes the ManyToOne referenced entity.
a) with annotation for the ManyToOne relationship in the main class: result - "Could not determine type" for the column.
b) with the annotation for the ManyToOne relationship moved to the pk class referenced by IdClass: result - infnite loop again.

Is there ANY way to make this work?


EDIT: I apologize for the bitchy tone of the above - I was just frustrated.

I have a situation where a class has a primary key consisting of two foreign key references.

Heres the code for the class:


And here is the code for the primary key:



This seems to be more or less what you want to do, so maybe you can use a similar approach.

Thanks for the response.

Does that mapping work for cascades? I tried something along those lines, but setting updatable and insertable to false on the relationship declarations broke cascading inserts.

-Sean

I haven't tried cascades, but i think the cascade declarations would have to be on the entity object, not the PK.

I think it goes wherever the ManyToOne/OneToMany declarations go. So if you move those to the PK, the cascade declaration would live there.

I suppose you could use the standalone @Cascade annotation instead, if you want to separate them.

In any event, the infinite loop was happening on lookup, not persist, so it shouldn't matter.

I have the @ManyToOne declaration on both the PK and the entity. They map to the same columns. insertable and updateable are false on the PK, but not on the entity.

I wrote a Crirteria query to fetch records and it throws SQLServerException: The multi-part identifier "user1_name" could not be bound.

The query is:

-------------------------------------------
Criteria criteria = getSession().createCriteria(Membership.class)
.createAlias("user", "user")
.add(Restrictions.eq("user.name", "kannan"));

criteria.list();

-------------------------------------------

I looked at the sql query and it had:

select this.user_id, this.group_id from Membership
inner join
User user where ...
inner join
Group where ....

and
user1.name = ?

clearly, user1 is not bound. it should have been user. can someone help me solve this problem?

thanks,
kannan