如何不使用EF（存储库模式）在.NET MVC3中重复数据访问规则？

Question

I have 2 classes with one-to-many like this:

public class Parent
{
  public virtual List<Child> Children {get; set;}
}

I am also using repository classes for each model, ie:

Parent has it's own repo class that has a Get() function that can gets an ordered list of Parents.

Child also has it's own repo class tha thas a Get() function that can gets an ordered list of Children that have a status of Active.

The problem is, the way EF works, since Parent has a reference to children, EF loads Children automatically when the parent list is loaded, but it gets active and inactive Children (also, the children list is not ordered). The check for active status is only in the Child repo.

How can I limit my repetition of "get" rules to be used wherever Children are accessed.

I know I can just modify the Parent repo to also check for Child status=Active, but then I am repeating my logic in every class that has children...

Edit: I have a Repository class for Child that returns an Ordered list of Children:

    public List<Children> GetList()
    {
        IQueryable<Children> query = context.Set<Children>();

        return query.OrderBy(a=>a.Seq).ToList();
    }

That works fine when I just need to access the Children directly. But when I need to get a Parent class, I use the repo function below:

ParentRepo GetByID:

public Parent GetByID(object id)
    {
        IQueryable<Parent> query = context.Set<Parent>();

        Parent parentModel = context.Parents.Where(a => a.ParentId == (int)id)
            .Select(a => new
            {
                Parent = a,
                Children = a.Children.OrderBy(b => b.Seq)
            }).ToList()
            .Select(q => q.Parent)
            .Single();

        return parentModel;
    }

As you can see, I had to order the Children here as well (by Seq).

This is the only way I can think to make this work, but it doesn't seem right.

public Parent GetByID(object id)
    {
        IQueryable<Parent> query = context.Set<Parent>();

        Parent parentModel = context.Parents.Single(a => a.ParentId == (int)id);
        parentModel.Children = childRepo.GetList(id);
        return parentModel;
    }

Answer 1

The repository pattern abstracts the data access layer, so that the rest of the application doesn't depend on DAL implementation details. The repository should be constructed according to the application needs . Basically you should design the repository interface from the application point of view and the repository should return domain/business objects.

If I understand correctly what you're doing, you're trying to build repositories around EF which gives you this kind of problems.

I might've misunderstood and it might be simply a EF related problem but it really seems to me that the problem is the wrong design of the repository.