I should have time to review your Linq patches this week...
On Nov 21, 1:33 am, Patrick Earl <[email protected]> wrote: > Hi all. > > While I'm thankful for all the work that was put into the Linq > provider for this release, I'm rather disappointed in how the beta > cycle has gone. We're facing release, and there are still many very > important issues that haven't even been commented on in the Linq > area. To give you some idea, in the entire beta period for the large > chunk of code that the Linq provider is, only 4 issues have been > resolved. During that same period, 25 new issues were created with > virtually no activity on them. To give you some idea of what I'm > talking about, here's a sampling of the issues. > > Numerous people have filed and voted about parameters not having the > correct type: > NH-2222 > NH-2234 > NH-2244 > NH-2394 > A patch is available in NH-2394, without a single pertinent comment. > > The null handling is another area with clear problems. You likely > remember the long messages on the mailing list. There were also very > few tests related to null handling, and numerous bugs. Despite the > provider clearly handling nulls incorrectly, there has been no action > on these issues. > NH-2370 > NH-2398 > NH-2402 > Again, there is a full patch with extended tests in NH-2402, but not > even a single comment on this important issue. If NH goes to release > without resolving NH-2402, it will cause breaking changes in the > future. > > There are many Linq issues with patches and tests. I'll just name > NH-2403 since I submitted it. Again, there has been no attention. > > Maybe I'm annoying, but I do find it quite frustrating when about the > only thing that's progressing is the version number and the same bugs > and limitations are still present. I've been happily using NHibernate > for years, but it truly is disheartening when even serious / popular > issues with full code and tests aren't addressed in any way. > > Patrick Earl
