Best Practices | Where to put search logic if we have different repository for each entity [closed]

Question

I am working on an application in which have different repositories for different entities and now i have to put search logic, hence i am confused where should i put my search logic, should i create a new repository for search or should i put the logic in the existing repository, and if i should put in some existing repository the which one is it.

the repositories are listed below

public class VendorRepository
{

}

public class ProductRepository
{

}

Public Class ProductBatchRepository
{

}

Answer 1

Why not a base repository? Something like this:

public class GenericRepository<T>
{
    protected IDbSet<T> Query<T>()
    {
        return myContext.GetDbSet<T>();
    }

    public IEnumerable<T> Where<T>(Expression<Func<T, bool>> predicate)
    {
        return Query<T>().Where(predicate).ToList();
    }

   ...
}

and then the repositories:

public class ProductRepository : GenericRepository<Product>
{

}

public class VendorRepository : GenericRepository<Vendor>
{

}

Answer 2

Alternative approach that I like to use...

...you could seperate commands from queries. Your commands would use the underlying domain model and repositories (as you have it now?); while your queries could use another technology; for example; query the database directly using entity framework code first.

This way you have all the flexibility of querying (using LINQ) and bypassing layers that don't add value to query purposes, and design the return types specifically for your clients. You can even use database views if that would make it easier to query.

Answer 3

I would create methods for searching every entity in respective repository and create another class that would call all of them to search everything and transform the results in the desirable shape ...