Hi Forwarding this from nhusers. Since we just generously released an re- linq update for NH, I feel I can get away with some advice ;-)
True, there is no way you'll compile a list of every possible thing that does not work in LINQ to NH. But: - There are a few major features missing, like (AFAIR) outer joins. Documenting the main unsupported features in the docs/home page would help a lot to set expectations. - Every unsupported feature should eventually result in a sensible error message that tells the user what just happened. (Is this just not supported? Only in a certain fashion?) - That would in fact be a very cool feature for something like NH 3.1. It's the trying and guessing that ultimately kills the fun in using LINQ. Right now, every failing LINQ query seems to result in a request at nhusers. And you can't blame the users, it's often really hard to tell just what is wrong. But that looks hardly sustainable to me. Will I be granted another advice? It's just an old pet idea of mine: Help your users by making the translation from LINQ to HQL visible. Many experienced NH users will easily spot troubles if they look at the HQL that's been generated. It's also much easier to discuss transformations that way. Just render the HQL tree as text, log it and put it into exception messages. I bet it will pay off soon. Just my two cents, Stefan ---------- Forwarded message ---------- From: José F. Romaniello <[email protected]> Date: Feb 8, 3:08 pm Subject: State of LINQ? To: nhusers No because it will be a hard as hell to discover all the things it doesn't support. The best list of known bugs is in the issue tracker:http:// jira.nhforge.org 2011/2/8 epitka <[email protected]> > Jose, thanks for answer, is there a list of things of what it does not > support? > On Feb 7, 5:37 pm, José F. Romaniello <[email protected]> wrote: > > It is stable and production ready, but a linq provider that support > > 100% of the cases is nothing but a dream. > > If you are planning to upgrade from the old provider, your tests will > > tell you how good this provider is. > > 2011/2/7, epitka <[email protected]>: > > > So, I've been absent from NH scene for a while, and now coming back. > > > I was wondering if LINQ provider has been now re-written and is it > > > part of NH, and if it is stable? > > > -- > > > 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. > > -- > > Enviado desde mi dispositivo móvil > -- > 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.
