Databases
StackOverflow2013
Postsdbo
POBest Repository Pattern for ASP.NET MVC
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest Repository Pattern for ASP.NET MVC
    primarykey
    data
    text
    <p>I recently learned ASP.NET MVC (I love it). I'm working with a company that uses dependency injection to load a Repository instance in each request, and I'm familiar with using that repository.</p> <p>But now I'm writing a couple of MVC applications of my own. I don't fully understand the hows and whys of the repository my company uses, and I'm trying to decide the best approach to implement data access.</p> <p>I am using C# and Entity Framework (with all the latest versions).</p> <p>I see three general approaches for handling data access.</p> <ol> <li><p>Regular DB context within a using statement each time I access data. This is simple and it works okay. However, if two locations need to read the same data within one request, the data must be read twice. (With a single repository per request, the same instance would be used in both places and I understand the second read would simply return the data from the first read.)</p></li> <li><p>A typical <a href="http://www.asp.net/mvc/tutorials/getting-started-with-ef-using-mvc/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application">repository pattern</a>. For reasons I don't understand, this typical pattern involves creating a wrapper class for every table used from the database. That seems wrong to me. In fact, since they are implemented also as interfaces, I'd technically be creating two wrapper classes for each table. EF creates tables for me. I don't believe this approach makes sense.</p></li> <li><p>There is also a <a href="http://www.tugberkugurlu.com/archive/generic-repository-pattern-entity-framework-asp-net-mvc-and-unit-testing-triangle">generic repository pattern</a> where a single repository class is created to serve all entity objects. This makes much more sense to me. But does it make sense to others? Is the link above the best approach?</p></li> </ol> <p>I'd love to get some input from others on this topic. Are you writing your own repository, using one of those above, or doing something different altogether. Please share.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJonathan Wood
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest Repository Pattern for ASP.NET MVC
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest Repository Pattern for ASP.NET MVC
      1. USMalaise
      1. VTFavorite
    3. VO
      singulars
      1. POBest Repository Pattern for ASP.NET MVC
      1. USShyju
      1. VTFavorite
    1. COI would say the link in number 2 is not a typical repository pattern. Typically, you have a repository for each Aggregate Root in [DDD](http://en.wikipedia.org/wiki/Domain-driven_design) speak. This is a good [SO thread](http://stackoverflow.com/questions/1958621/whats-an-aggregate-root) on this topic. The example in number 2, as you mention, seems to just wrap a table. It looks like they are implementing the pattern just to implement the pattern with no real benefit. So I would agree with you.
      singulars
      1. POBest Repository Pattern for ASP.NET MVC
      1. USRobertMS
    2. COYou may be right. However, in searching the web, most of the examples I found created separate wrappers for every entity, including those in some books I have. In that respect, the code at the link I posted seemed typical. Thanks for the links. I'll check them out.
      singulars
      1. POBest Repository Pattern for ASP.NET MVC
      1. USJonathan Wood
    3. CO@JonathanWood Here's the [solution I like best](http://huyrua.wordpress.com/2010/07/13/entity-framework-4-poco-repository-and-specification-pattern/) (damn, I use this link a lot). Namely, the non-generic repository interface with generic methods. It's still a relatively thin wrapper around the `DbContext`, but it allows for easier testing.
      singulars
      1. POBest Repository Pattern for ASP.NET MVC
      1. USPatryk Ćwiek
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload