IEntityRepository

This EntityRepo class contains the Persistnece Logic that is not covered by the GenericRepository.
Following Sample project does not use the GenericRepo but it sould be in the project to encapsulate the General CRUD logic need by Every Entity.

=============================

using System.Collections.Generic;
using GigHub.Core.Models;

namespace GigHub.Core.Repositories
{
    public interface IGigRepository
    {
        Gig GetGig(int gigId);
        IEnumerable<Gig> GetUpcomingGigsByArtist(string artistId);
        Gig GetGigWithAttendees(int gigId);
        IEnumerable<Gig> GetGigsUserAttending(string userId);
        void Add(Gig gig);
        IEnumerable<Gig> GetUpcomingGigs(string searchTerm = null);
    }
}

=======================================

using GigHub.Core.Models;

namespace GigHub.Core.Repositories
{
    public interface IFollowingRepository
    {
        Following GetFollowing(string followerId, string followeeId);
        void Add(Following following);
        void Remove(Following following);
    }
}



Comments

Post a Comment

Popular posts from this blog

IGenricRepository

Image
public interface IRepository<T> { IEnumerable<T> GetAll(); IEnumerable<T> Find(Expression<Func<T, bool >> query); T GetByID( int id); void Add(T item); void Update(T item); void Delete(T item); } public interface IGenericRepository<T> where T : class { IQueryable<T> GetAll(); IQueryable<T> FindBy(Expression<Func<T, bool>> predicate); void Add(T entity); void Delete(T entity); void Edit(T entity); void Save(); }
Read more

Summary of All Data Source Patterns

Simple Active Record (No Repository ) == RDG++ Simple Data Mapper (No Repository) ==  TDG++ Respository Based Active Record = Simple Active Record++ Repository Based Data Mapper = Simple Data Mapper++ Respository (Active Record) = Simple Active Record++ Repository (Data Mapper) = Simple Data Mapper++ When we are using ADO.NET and writing our own DAL, we are not using any ORM. We are dealing ourself with all dirty work of Data Access Writing SQL,Connections, Resultset fetching n mapping, exceptions, messaging, casting, transactions,updating the database schema and domain model ourself ORMs try to abstract these things out and make our life easy Linq like language for quering data. No connection management No Result set dealing and mapping to Domain Model No exception handling No messages to upper layers No Data type casting No Transation Mgmt, it is done by UOW and Change Tracker Database schema and Domain is synched by Code First Migrations Two Types of ...
Read more