Hibernate version:
2.0.6

How come many-to-one only supports cascade

none|all|save-update|delete

Whereas

Set, Map etc etc support

none|all|save-update|delete|all-delete-orphan|delete-orphan

I am mapping a users details as a many-to-one class with
unique=true ... this works fine but orphans are being left
behind.

It would be cool if the all-delete-orphan & delete-orphan
were supported for this.

I have worked my way arround it now but it just strikes me
as something that would be cool to have consistent.

Rgds

Bryan

How would Hibernate figure out what object has been removed from a detached object?

Besides, cascade delete on a many-to-one is always semantically extremely suspect. (it would make sense for one-to-one, though).

I am specifying the unique attribute so in reality it is a one-to-one
the problem with a one-to-one though is that the object that is
the primary key of the object which references the dependant
object is created using the generated method.

I have an object with several one to one attributes.

I would model them as custom types but for the fact that each contains
an array eg

SystemUser --- SystemUserDetails (one-to-one)
SystemUserDetails contains an array of Address objects.

Perhaps I am just not fully familliar with hibernate and
am doing this in an overly complicated manner.

My DAO code is unnecessarily complicated by this approach though
as I have to do the following to ensure there are no orphans left
behind.

snip=
public void updateDetails(SystemUser user, SystemUserDetails systemUserDetails) {
logger.debug("updateDetails called");
SystemUserDetails originalDetails = user.getSystemUserDetails();

if(originalDetails != null) {
systemUserDetails.setId(originalDetails.getId());
}

user.setSystemUserDetails(systemUserDetails);
..................
=snip


--b

i am going to try doing this with a component instead.

I amn't sure if it has the same problem with orphans though.

--b

A quick look at the documentation suggests that a component
cannot contain an array . Is this correct ?

--b

here for example is what has to be done in order to work with this
without creating loads of orphans.

public void updateMyDetails(SystemUserDetails systemUserDetails,
String username) {

//get the Session instance already bound to current thread and opened
Session session = SessionFactoryUtils.getSession(getSessionFactory(),
false);
try {
SystemUser systemUser;
List list = session
.find(
"From SystemUser as systemUser where systemUser.username = ?",
username, Hibernate.STRING);
if (!list.isEmpty()) {
systemUser = (SystemUser) list.get(0);

SystemUserDetails originalDetails = systemUser
.getSystemUserDetails();

if (originalDetails != null) {
systemUserDetails.setId(originalDetails.getId());
}
session.evict(originalDetails);
systemUser.setSystemUserDetails(systemUserDetails);

session.update(systemUser);