- File issues when you find bugs. http://jira.nhforge.org/
- Vote for issues. Popularity is difficult to gauge if we don't hear back from people.
- Provide test cases for those issues. A complete test case is easier to digest than a tiny code fragment without context. If the test can be used directly, the team member working on the issue can spend more of their time making improvements instead of trying to recreate a test.
- If you're feeling ambitious, dig into the source code and try to work out a fix.
There's a great article on making tests for NHibernate here. I've also included some different steps that might help you out.
- Check out the trunk using something like TortoiseSVN (https://nhibernate.svn.sourceforge.net/svnroot/nhibernate/trunk/nhibernate)
- Use ShowBuildMenu.bat to create the AssemblyInfo.cs files.
- Load up NHibernate.Everything.sln in Visual Studio.
- Create a test with the issue number in the NHSpecificTest folder of the NHibernate.Test project (NH2392 is a fairly simple example to copy from).
- Use ShowBuildMenu.bat to see how to set up your database connection and run all the tests.
- Create a patch (TortoiseSVN can help you with this) and attach it to the JIRA issue.
I'm happy to see that someone admits that the LINQ provider is still in a beta state. I don't understand why NHibernate 3.0 has been released. The most important improvement in this release is the new LINQ provider. In my mind, with the LINQ provider in this state, the NHibernate 3.0 GA is a NHibernate 3.0 beta 3 !
ReplyDeleteI have also been really disappointed when I first run some queries with the new linq-provider, seeing the poor SQL it generates in NHProf. IMHO the provider is far from being production-ready in enterprise-environment.
ReplyDeleteSimple CRUDs are fine, but when I need to have clear and readable SQL-output, I always "fall back" to QueryOver, which is currently the best way to go with NHibernate.
Hi d.lang. I'd be quite interested to know what aspects of the generated SQL you found particularly disturbing.
ReplyDeleteWe have made some improvements for the 3.1 version, which is being released imminently. Admittedly though, you aren't likely to see major differences in the query structure, so I am quite curious what the main problems you see are.