Does it makes sense to use the Repository pattern without the use of LINQ or some other ORM? I am writing an application in MONO and using MySQL, was thinking of using the repositoy pattern but not going to be able to deal with IQueryable. I was thinking of just exposing more methods on the repository to make it obvious that filtering was going to happen on the db side with the repository call. Any suggestions if that is a valid use of the design or any other design ideas instead?
Mysql – Repository Pattern without LINQ or other ORM
- C# – How to create an Excel (.XLS and .XLSX) file in C# without installing Microsoft Office
- C# – How to get a consistent byte representation of strings in C# without manually specifying an encoding
- Git – How to clone a subdirectory only of a Git repository
- Git – How to clone a Git repository into a specific folder
- Git – Remove a file from a Git repository without deleting it from the local filesystem
- Git – How to push a new local branch to a remote Git repository and track it too
- Php – Proper Repository Pattern Design in PHP
- C# – Why not inherit from List
Repository has nothing at all to do with IQueryable. What you are thinking of is the Rob Conory .net 3.5 take on the repository pattern, which is actually more of a data broker pattern.
A repository is responsible for returning objects, and deals with data access so that the rest of your application can remain ignorant of it.
You can see a very high level description on Martin Fowlers site