I have a problem when using the table-per-subclass mapping strategy. I have a class Parent and a class Child. The Child class is a subclass of Parent. In the Parent's mapping file, Child is defined as a joined-subclass. There is no other relationship defined between the Parent and Child.

There is a case in my application that a Parent record will be created first, then I need to create the corresponding Child in a different time. The problem I have is when I call session.save(aChildInstance), Hibernate tries to insert both records (into the two tables) and blows up because Parent already has a record with the pk. When I call session.update(aChildInstance), Hibernate tries to update both records and blows up because the Child is not in the database yet. The behavior of saveOrUpdate is the same as update.

Any help is greatly appreciated!

Weiguo

can you use encapsulation rather than extension?

b

Thanks a lot for the reply. There are valid reasons to use inheritance in this case. If there is no way to get around it, I might have to resort to straight jdbc, or even creating different mapping just for this purpose. Still it makes sense to use inheritance.

I am hoping this is something that could be done in hibernate.

Weiguo

what happens when you use session.saveOrUpdate()

b

oh never mind. i just read the rest of your first post.

b

are you calling saveOrUpdate on parent or child.

b

on the child. One thing I should have mentioned is the object is passed in from a different layer. The child object obviously has all the data I need for the operation. Thanks.