Theoretically, is it ok to get Hibernate generate sql commands which break it's own generated table structure's index? I regenerated the structure with the current mapping from scratch (not that it changed, but to make sure), but I still get Oracle errors: ORA-02292: integrity constraint (VOIP_RATER.FK3596FCCC38F0C7) violated - child record found

Of course I'll start and debug the problem in my 1-n relations and the way I remove entities participating in relations, but I really wonder if hibernate should or should not behave like that. If it's a bug, I'll try and help tracking down the problem..

thanks,
dyn

Hibernate does not usually cause foreign key constraint violations.

The only case in which it really happens is when deleting (which is something we cannot possibly fix!).

It happens on delete.. okay I'll fix it on my own.

Thanks,
dyn