Or more humbly put, the power of IQueryable and Linq is that it gives the developers a productive and strongly typed query syntax, where skills, not code, can be brought over to different data scenarios.
It is already a well known fact that in-memory Linq behaves quite differently from "Linq to SomeDataBase", and L2S, EF and NH should be treated as "equally different" from each other. There may be perfectly valid reasons to put NHibernate behind a wrapper, such as limiting the range queryable types, but I can tell you from real experience in two concurrent projects (one with NH, the other with L2S) that a generic IRepository<T> is a really crippling concept. If you want a data source agnostic data layer (extremely rare), you're better served by a much more explicit abstraction, e.g with methods like "GetNewsForHomePage". That said, your need for string based Dynamic LINQ must have other reasons. What is the scenario? /G 2011/6/9 Fabio Maulo <[email protected]> > "IRepostiory could be Linq-to-sql, Entity Framework or NHibernate." > In your imagination perhaps, in the real world no. > > Just put an enum in your domain and then try to use it with Linq2SQL or > EF4. > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/nhusers/-/gVTGfwC8XtoJ. > > 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. > -- 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.
