Those are all good points. Have you attempted to run exactly the test you mention in the trunk in release mode --? And if so, what are the results?
Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Thu, Jun 2, 2011 at 11:56 AM, Beefy <[email protected]> wrote: > I understand a unit test makes your lives easier. As I said though, it > really doesn't seem like I am doing anything here, though, as Ramon > points out, I MUST be since it isn't working. My unit test is simply > going to be something along the lines of > > Session.Query<T>().Where(x => x.someProperty == > "someValue").SingleOrDefault(); > > And that's pretty much it. My problem here is not that there is a bug > in NHibernate, but that I need help trying to track down what is > different in my implementation. A unit test such as this adds no > useful information to your testing suite, as I would suspect you > probably already HAVE a unit test that does exactly what I would do. > In fact, browsing the repo, I see you DO have exactly the test I would > do (granted, with LINQ commands instead of LINQ method chains), in > nhibernate/src/NHibernate.Test/Linq/WhereTests.cs. > > If that test runs in Release mode ok, then obviously there is not a > bug in NHibernate, but in my implementation. > > What I am asking for is help in figuring out where MY issue is. As the > NH Users group was unable to offer any assistance, I had hoped that > perhaps someone here would be able to help me out. If no one here is > willing to render such help, or I am asking in the wrong place (As I > may be), then I will gladly seek help elsewhere.
