repository-pattern

We are working on a Restful project with lots of DB tables. Though the operations on the tables are almost same and mainly INSERT/UPDATE/DELETE/FETCH. my questions is: will we have to create a repository (extending JpaRepository) for every entity (Domain class) we create or, there is an option of creating a GenericRepository that can handle all the above-mentioned functionalities for all the entities? i.e a single GenericRepository for all. if so, could you share an example? is [there] an option of creating a GenericRepository that can handle all the above-mentioned functionalities for all the

I am using Entity Framework and would like to create generic GetById method in Repository class with eager loading: Here is my method which uses lazy-loading: public virtual TEntity GetById(object id) { return DbSet.Find(id); } I know method Find does not support eager loading, but how it is possible to modify this method to use eager loading, so that I use this method as follows(for an example): _unitOfWork.MyRepository.GetById(includeProperties: "Users"); One possible way is to use FirstOrDefault with predicate over the DbSet with Include s. It's not hard to build manually a predicate using

I found an example of Generic Repository which is based on Entity Framework and trying to understand how to automatically resolve repositories by the same interface and entity type. The link above leads to the repo where you can see the following approach: public class HomeController : Controller { private readonly ICategoryRepository _repository; public HomeController(ICategoryRepository repository) { _repository = repository; } in this case we have to create a separate CategoryRepository - so, repository is per type . That means we end up having a lot of classes for repositories. I would

In an application, there are at least two ways for dealing with domain object persistence and an ORM. Mapping directly the domain object to persistence using some kind of ORM (xml or annotations) Making separation of concerns in case of a lot of impedance mismatch between your domain and your persistent model (table columns). That means, domain object is persistence agnostic and there are some conversions to some corresponding persistent object, this latter maps to an ORM. As pure DDD developers know, domain should not be driven by your database needs, thus in my project, I use this separation

I'm using the repository pattern. I have a Country repository that I'm using a service to submit. Where should I put the check to see if the country already exists in the database, I throw an exception? Is there a way to do this in one database call? (Check and insert if non-existent)? If this is possible, could it be done in the service layer? (if that is where you recommend I do the checks). Because of multi-user concurrency, you can't SELECT then INSERT and be guaranteed of no problems. So the solution proposed by @Coding Gorilla could fail in high concurrency situations. You should put a

I am creating an Intranet website with ASP.NET MVC and Onion Architecture . I have been implementing the repository pattern but I have a difficulty. Let's say I have a Document table with IDDocument in it. Then this is my repo(with just one method): class Repository<T> : IRepository<T> where T : class { private readonly PrincipalServerContext context; private DbSet<T> entities; //Constructor and stuff here public T Get(long id) { return entities.SingleOrDefault(s => s.IDDocument == id);//Here is my problem } } The problem is that I cannot use this since T is not recognized as being from

The repository pattern suggest that you can only pull aggregate roots. But how would you retrieve a single child using only it's uniqiue identity(Child.ID) if you do not know it's parent(root)? class Parent { public int ID { get; set; } IEnumerable<Child> Children { get; private set; } } class Child { public int ID { get; private set; } public virtual Parent Parent { get; private set; } // Navigational model } My application is stateless (web), for simplicity, the request only contains the ID of the child. I am thinking three approaches: Call all the parents then ask them politely who owns