Hibernate version: 3.1

I do have a father object containing a collection of children, with a cascade set to "all-delete-orphan".

When I do a saveOrUpdate() on a newly created father, (ie: not in session), the children are correctly cascaded. For instance I could retrieve their database id (generated with "increment") just afterwards.

But if I modify an existing father (in my case, clearing the collection, and adding some children), and do a saveOrUpdate on the father, the children id are not set. (cascade not made ?)

I do have to wait after the session.commit() to be able to get the children id. But in my design I need to get this id after the saveOrUpdate(), not after the commit().

Note that my father does not have nay other value changed. Only the elements in its collection.

Is it a known behavior? Do I have to browse myself the hierarchy, and manually save each of the children?

--
Hugo

generally speaking needing the ID in some cases is bad design in my opinion. Although in some cases it is needed.

However, you can use session.flush() instead of commit to get your ids populated.

J

Hi
probe with the inverse clause, add inverse in true in the bag declaration, and add in the child mapping the many-to-one clause
and intent again

I forgot

If you have to persist an object and use it Id not use session.save(Object);
use
session.persist(Object);

is saves the object and the set it's identifier Id.

Thanks for the replies. I replaced my "saveOrUpdate()" with a "persist()" and every things seems ok now. I could get the id just after the persist(). Good news for me ;)

Some comments anyway:

I agree with that, but I really need that children ID for speeding up some external index process, and I need it before the "commit()" to be able to rollback if something goes wrong.


I already use a inverse relation, so this was not the reason of the cascade failure. (I did not post my mapping files sorry for that, but I wasn't sure they'll be usefull, since this is a very general problem).


Final note, the hibernate documentation is not so clear about that problem. I was not able to find a clear distinction between "saveOrUpdate()" and "persist()".

And I found some inconsistency between the documentation and the actual code behavior. The docuementation says:

but according to the definition of saveOrUpdate() :