When foreign key constraints are set (on delete=cascade etc.), those constraints are not reflected in the database. Only the foreign key references are set (alter table TABLE_NAME add constraint CONSTRAINT_NAME foreign key ( COLUMN_NAME) references FOREIGN_TABLE_NAME)
Hence, in the database, the default remains (On Delete Rule NO ACTION). In the generated hbm.xml, however, the cascade is defined as it should ( <bag cascade="all".../> ) Am I missing something, is this feature not supported or is there a bug? I am using fluent nhibernate 1.3.0.733, nhibernate 3.3.3.4000, Firebird ADO.NET Data provider 3.0.2.1. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
