I'm looking to save a basic Parent/Child object graph, where the Parent's Primary Key is not determined before the saving the Parent or the Child records (I'm using MySQL's auto increment feature that gives the next Primary Key for the Parent record upon record insert).

With this in mind, when Hibernate attempts to persist the entire object graph, it successfully inserts the Parent record, but fails on the Child records b/c the Child records do not contain the Primary Key value of the Parent (I obviously cannot set this value while constructing my Child domain object b/c it is unknown until record insert).

My Child table contains a compound Primary Key, which uses the Parent's Primary Key as one of it's key values - hope that makes sense. The Child table is basically just an association table.

I am using in my Parent .hbm doc.

I am also using in my Parent .hbm doc.

Lastly, I'm also setting the Parent record into each Child record (per the documentation).

Any idea how to tell Hibernate to use the Primary Key of the Parent as part of the compound Primary Key of the Child? I hope all this makes sense... I think I've read it back to myself about 50 times to make sure it sounds correct...

parent mapping
<set name="authProfileSet" inverse="true" cascade="save-update">
<key column="user_id"/>
<one-to-many class="AuthProfile"/>
</set>

child mapping
<many-to-one name="person" column="user_id" class="Person" not-null="true" />

so, you might have
person.setAuthProfile(Set authProfile)

now, you can extend your parent class with method that add the child.

public void addAuthProfile(AuthProfile authProfile) {
Set<AuthProfile> authProfileSet = getAuthProfileSet();
if (authProfileSet == null) {
authProfileSet = new TreeSet<AuthProfile>();
setAuthProfileSet(authProfileSet);
}
authProfile.setPerson(this);
authProfileSet.add(authProfile);
}

when you save the person, the save action should cascade to the child. I haven't test it out, let me know if it works.
thanks

Well, I gave that a shot, but it didn't seem to work...

Not sure where to go from here, so I thought I'd post my code. As you'll see, the hbm docs below were created by the Hibernate Tools. I reverse engineered the database to create the hbm docs and the POJO's - pretty damn sweet! - but maybe that's part of my problem - not sure...

Here's the Parent .hbm doc:



And the Child .hbm doc:



And the PaymentTypes .hbm doc:



And the code to create the Object Graph in my Controller:



And part of the stack trace:



So it appears as if Hibernate does not automatically set the Parent's Primary Key (i.e., item_id) to the Child record's composite Primary Key...

Any help is greatly, greatly appreciated, as this one has had me stumped!

Thanks a lot,

Matt

Oh yeah, one more thing.... In my controller, I also tried the following:

ItemsPaymentTypesId itemsPaymentTypesId = new ItemsPaymentTypesId();
itemsPaymentTypesId.setPaymentTypeId(new Integer(paymentTypes[i]));
itemsPaymentTypesId.setItemId(item.getItemId());
ItemsPaymentTypes itemsPaymentTypes = new ItemsPaymentTypes(itemsPaymentTypesId);
itemsPaymentTypes.setItems(item);
mySet.add(itemsPaymentTypes);

But that didn't work either... I thought upon insert of the Parent, Hibernate would propagate the Parent's Primary Key down to each Child record automatically. This seems so basic - I just don't understand why this is isn't working...

I have the same problem. Have you fixed yours? If so, how?

I too have hit upon this problem. Can you please post how you resolved this issue?