Hi,

This should be a simple problem, but it's driving me crazy. I have a parent class with a one-to-one unidirectional association to another class. Primary keys are the same, but are assigned, so I need to set them manually in each class.

mapping in the parent class is:

<one-to one
name="child"
class="xxx.xxx.child"
cascade="all"
outer-join="auto"
</>

There is no association mapping in the child since it's unidirectional.

My problem is that when starting out both parent and child are transient. I set the child in the parent, and do a session save. Looking at the SQL, hibernate is doing an insert on the parent object, but it does an update on the child object. Since the child object is transient too, there is nothing to update and the child class isn't persisted; the SQL needs to be an insert, not an update.

Anyone have any idea how to make this work via a cascade (don't want to save each one separately).

just add and unsaved-value="any" to the id of the child and this solves the problem. If it still does not the post the mapping files and pojo's and the code where you are tyring to set the child

Thanks, but unsaved-value wasn't a attribute of one-to-one (got a mapping exception).

Forgot to mention I'm using version 2.18.

What I can't understand, is that I'm specifically calling a save() method, not an update() or a saveOrUpdate(). One would think that would force hibernate to use a SQL insert on all the cascaded objects too.

The unsaved-value is an attribute of the "id" tag, not the "one-to-one". You need to set the unsaved-value attribute on the id tag for the child. You should setup the unsaved-value to have a value that will be the equivalent of "uninitialized" in ur application. For e.g. if i have an employee class, i would know that no employee will have id = -1 , so id set my id to have an attribute of
unsaved-value = -1

HTH

Thanks, that did the trick.

I'll need to dig up an explanation of what the unsaved-value is actually doing.

It was only a work around, but I found that using a saveOrUpdateCopy also solved the problem, but since that method uses extra calls to the database (it does a select before hand to figure out if the object is transient or persistent), it would have increased overhead.

Thanks again.