Hi All,

here is a brief description of the problem I'm facing -

A Product can have many ProductAttribute.

class Product {
@OneToMany(targetEntity = ProductAttribute.class, fetch =
FetchType.EAGER, cascade = {CascadeType.ALL})
@JoinColumn(name = "Product_ID")

public Set<ProductAttribute> getProductAttributes() {
return productAttributes;
}
}


Now when i delete the Product, its setting the PRODUCT_ID in the PRODUCT_ATTRIBUTES table to NULL instead of cascading the delete to the ProductAttribute. I want all ProductAttribute to be deleted when the associated Product is deleted

thanks

specifying updatable=false on the joincolumn fixed my problem.
Now off to figuring out how to prevent the (n+1) sqls that is being fired to perform cascade delete

But I had to figure out that in XML config I need to set the attribute for key
. I suppose this corresponds to teh JoinColumn annotation.

Still I wonder about the number of placed hibernate gets informed that an attribute key-field is not-null and also part of the PK - and still attempts to perform

use cascade DELETE_ORPHAN (check the doc)