On Saturday, January 18, 2014 12:05:22 PM UTC-6, Oskar Berggren wrote: > > Without having looked at the code, I agree that exceptions shouldn't be > used in that way. I'm sceptical to your timings - is 10ms the pure > ADO.NETtime? Because NHibernate does a lot of things that could account for > the > 70ms. I suspect it's highly unlikely that the exception alone adds 60ms > with no debugged attached (or even with the debugger). > > I'm running in a VM, and inside the debugger using SQLite as the database, so all of that may be a factor. I will run more tests on my host machine outside the debugger to see what performance impact the exception has in a more real world situation.
> If you have a good quality fix for the issue, I don't see why it shouldn't > be fixed. > Thanks, I will consider submitting the issue once I find out more. > With LINQ subqueries: > var childQueryable = session.Query<Child>().Where(child => ...).Select( > child.Parent.ID); // No ToList! > var parents = session.Query<Parent>().Where(parent => > childQueryable.Contains(parent.ID); > > /Oskar > > Thanks so much, I like this for a workaround! -- 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. For more options, visit https://groups.google.com/groups/opt_out.
