Hibernate version: 2.1

Mapping documents:


The mapping above is similar to p. 227 of "the bible". Notice that no cascade="delete" is set, as I simply want to disassociate Categories and Items, from both ends, and not delete in cascade.

If I delete a Category referred by an Item, the mn table CATEGORY_ITEM is updated ok, and no exception is thrown.
But if I delete an Item which is referred by a Category, the database throws a foreign key reference violation.

I found a workaround: simply do not put in the mapping, but the all the rest as in the inverse case: this way the mn table CATEGORY_ITEM is updated two ways
(but in this case the primary keys created by the schema tool on the mn table CATEGORY_ITEM may be the wrong ones, as the mapping order becomes relevant).

I wonder whether there is another way to do this, as this is clearly a trick.

after a nigth of meditation, I must make:

- a correction: the schema is created correctly, using bag as the inverse of the list

- an integration: this is not a trick, but the correct solution: with this solution when deleting an Item (or a Category), deletion of the association (but not of the associated) is performed automatically by Hibernate. Even by introducing a Composite, you will not get this

well, seeing it now this is quite misleading: for a proper model see the caveatemptor Categorizeditem persistence. the way proposed above is both "working against the framework", and using an object model less fine grained than the relational one, two bad sins.