Hi Frans, [...]
> VB.NET always adds the projection of a groupby query in the call > expression to GroupBy, C# compiler doesn't. This also creates cumbersome > code to obtain the real source of the groupby. I still have headaches > thinking about it... ;) I'm currently implementing GroupBy support in re-linq's new SQL backend. The backend is mostly feature-complete for now (and for SQL Server), the only important thing still missing is groupings-coming- via-subqueries, which I'm working on right now. Just wanted to say that I share your headaches... Of course, re-linq's front-end (which is what NHibernate uses) doesn't provide support for most VB-specific quirks - in the end, the back-end (NHibernate) must be able to transform the constructs into the target language (HQL). The GroupBy overloads with the result selector, by the way, are by default parsed by the front-end as if they were an ordinary GroupBy followed by a Select. So at least, the backend only needs to handle one case instead of handling two of them :) > The useless coalesce statements added by the vb.net compiler are > better stripped out as well, because they cause complex SQL which is > unnecessary. I didn't know about those. When do they occur? The rest of my answer was so long I turned it into a blog post: <http://www.re-motion.org/blogs/mix/archive/2010/07/16/making-it-hard- to-implement-language-compatible-linq-providers.aspx>. Regards, Fabian -- 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.
