Is is normal for Hibernate's auto schema ddl generation to generate two FK constraints when an association specifies cascade delete (@OnDelete(action=OnDeleteAction.CASCADE)). I get the following constraints:

alter table cal_property_index add constraint FKBA988E7927801F2 foreign key (eventstampid) references stamp
alter table cal_property_index add constraint FKBA988E79FD15B882 foreign key (eventstampid) references stamp on delete cascade

Shouldn't there only be the second?

-Randy

Nevermind, figured out the problem.

I was defining @OnDelete(action=OnDeleteAction.CASCADE) on the many-to-one association instead of the one-to-many (it is bi-directional).