Guys,

I'm a little confused about collections and deletions.

Say I have a class called Person, and that person has a list collection of Address objects.

If I manually delete an Address object from the database by calling session.delete(addressObj), is it then imperative that I get ahold of the containing Person object and do a person.getAddresses().remove(addressObj) as well, or can Hibernate do that for me?

I've searched the two books I have, the online manual, and the forum and haven't found an answer yet. I'm afraid the trees are impeding my view of the forest...


I appreciate any insight you can provide.

jbwiv

Your example does result in the in-memory state not matching the databases current state (after a transaction commited). This is usually not a problem but it depends on the application context. The same thing happens with other collection operations. You can make the state match if you wish but the effort is not always required. Alternatively, you could delete the address from the collection and let the cascade settings trigger the delete operation. Hibernate is flexible.