How do I keep the Advantages of IQueryable while using ViewModels or DTOs instead of ORM generated Entities?

When using Linq-To-SQL or Entity Framework, the DataContext and generated entities provide IQueryable interfaces for deferred execution. It lets me write code like this: public class RPO { DataContext dc; public RPO(){ dc = new DataContext(); } public IQueryable ReadData() { return dc.Data; } } public class Svc { RPO repository; public Svc() { repository = new RPO(): } public IQueryable ReadActiveData() { return repository.ReadData().Where(d => d.IsActive.Equals(true)); } public IQueryable ReadArchiveData() { return repository.ReadData().Where(d => d.IsArchived.Equals(true)); } } This model falls appart if in the class `Svc` I return `DataModel` instead of `Data` -- how can I keep `IQueryable` as far down the chain as possible?

以上就是How do I keep the Advantages of IQueryable while using ViewModels or DTOs instead of ORM generated Entities?的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » WebStorm

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准

联系我们

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏