If there is a query that is more complicated than fits into the FindAll using a selector method like mentioned in issue #59, a way around it is to create SomeCustomRepository : Ef5Repository, and get access to the DbContext property yourself to run your own query. But when doing that, there is no way to take advantage of the cache.
Let's see if there is a way that the user creating the custom repository can pass the query in and use a caching strategy if there is one setup.
Maybe a Query(IQueryable<>) method would be useful? Haven't thought that thru yet but worth looking at.
If there is a query that is more complicated than fits into the FindAll using a selector method like mentioned in issue #59, a way around it is to create SomeCustomRepository : Ef5Repository, and get access to the DbContext property yourself to run your own query. But when doing that, there is no way to take advantage of the cache.
Let's see if there is a way that the user creating the custom repository can pass the query in and use a caching strategy if there is one setup.
Maybe a Query(IQueryable<>) method would be useful? Haven't thought that thru yet but worth looking at.