Yes, if you port code from LINQ 2 objects (or LINQ 2 SQL even), some stuff will break. It would be pretty arbitrary to call that a breaking change however. Different providers have different capabilities. There's also a lot of stuff you can do in L2Objects but not in L2SQL. It is absolutely impossible to convert any possible C# code in SQL.
On Feb 10, 11:31 am, hoghweed <[email protected]> wrote: > I'm really sorry I didn't post the exact exception, but it was the classic > message "the method blabla is not implemented"... > My question is, is not possible till now as I saw, to know exactly which of > the Linq extension methods is no more supported? > So it's a big lie when it's said that the breaking changes are minimal... > this is related to the pure NHibernate usage... but referring to the > the linq syntax the breaking changes are massive number... -- 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.
