This error has been popping up frequently in my logs: "deleted object would be re-saved by cascade"
I have had no luck in replicating it however. As far as I know, I am never deleting an object of the specified type and neither am I assigning the object to two different collections or references. The problem does not occur frequently enough for me to realistically enable detailed logging using log4net. Is there any other things I can do to try and unearth what is causing this issue? For example, is it possible to acquire all the logs for an NHibernate session after an exception has occurred? Is it possible to print out an entire object graph so I can find out where the object has been deleted from and where it still resides? -- 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.
