I agree with you Jan in that it it not always possible to tell the DBAs to change things to accomodate NHibernate... really it has to be the other way around unless you are fortunate enough in a brand new development.
I think the behaviour I mentioned above would be a welcome addition to NHibernate behaviour but I don't know the code base to be able to add it in myself, and Fabio is the lead anyway so I presume NHibernate goes in the direction he believes is best. I presume from the comments above he doesn't think this is a big issue and I suspect he is quite busy at the moment. What you could try is writing a new stored procedure to do the delete and the cascade for you, and hook NHibernate to that procedure. I imagine most DBA's won't mind a new stored proc, as its something within their control. Look on this website http://www.summerofnhibernate.com/ Chapter 10 and this one http://davybrion.com/blog/2008/11/populating-entities-from-stored-procedures-with-nhibernate/ Good luck ! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
