That's an "if". If your DB doesn't support multiquery then you are stuffed.
Besides, even if your DB does execute on one trip, if NH submits 500 DELETE FROM z WHERE id = ? surely its still going to be slower than one DELETE FROM z WHERE z.ParentId = ? As I said, I'm convinced most people coming using Clear() for the first time expect it to do the latter whereas in fact it doesn't appear to. After all, that's what a Clear() does in .NET - wipes all instances from a collection. It makes sense for this to be replicated in the database. Orginally I thought it did the single shot delete and I've seen several other posts since then from people stating the same thing. Each time the answer is "its working as intended, raise a JIRA". Well it may be, but my question is "working as intended" really doing what it should? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
