Databases
StackOverflow2013
Postsdbo
PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
    primarykey
    data
    text
    <p>I am bit curious as to what experience other developers have of applying the Repository pattern when programming in ASP.NET MVC with Entity Framework or NHibernate. It seems to me that this pattern is already implemented in the ORM themselves. <strong><code>DbContext</code></strong> and <strong><code>DbSet&lt;T&gt;</code></strong> in the Entity Framework and by the <strong><code>ISession</code></strong> in NHibernate. Most of the concerns mentioned in the <strong><code>Repository</code></strong> pattern - as catalogued in <a href="http://martinfowler.com/eaaCatalog/repository.html" rel="noreferrer">POEE</a> and <a href="http://domaindrivendesign.org/node/123" rel="noreferrer">DDD</a> - are pretty adequately implemented by these ORMs. Namely these concerns are,</p> <ul> <li>Persistence </li> <li>OO View of the data</li> <li>Data Access Logic Abstraction</li> <li>Query Access Logic</li> </ul> <p>In addition, most of the implemententations of the repository pattern that I have seen follow this implementation pattern - assuming that we are developing a blog application.</p> <p>NHibernate implementation:</p> <pre><code>public class PostRepository : IPostRepository { private ISession _session; public PostRepository(ISession session) { _session = session; } public void Add(Post post) { _session.Save(post); } // other crud methods. } </code></pre> <p>Entity Framework:</p> <pre><code>public class PostRepository : IPostRepository { private DbContext _session; public PostRepository(DbContext session) { _session = session; } public void Add(Post post) { _session.Posts.Add(post); -session.SaveChanges(); } // other crud methods. } </code></pre> <p>It seems to me that when we are using ORMs - such as Nhibernate or Entity Framework - creating these repository implementation are redundant. Furthermore since these pattern implementations does no more than what is already there in the ORMS, these act more as <strong>noise</strong> than helpful OO abstractions. It seems using the repository pattern in the situation mentioned above is nothing more than <em>developer self aggrandizement</em> and more pomp and ceremony without any realizable techical benefits. What are your thoughts ??</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBikal Lem
    1. USBikal Lem
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
      1. USCarlos Muñoz
      1. VTFavorite
    3. VO
      singulars
      1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
      1. USJamie Dixon
      1. VTFavorite
    1. COI agree with the sentiment here (and [I'm not the only one](http://ayende.com/Blog/archive/2009/04/17/repository-is-the-new-singleton.aspx)), but "What are your thoughts" is the very definition of a subjective and argumentative question.
      singulars
      1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
      1. USJeff Sternal
    2. CO"creating these repository implementation are redundant" That is because they are doing it wrong. The repository *should* represent **domain** concepts, not generic CRUD.
      singulars
      1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
      1. USquentin-starin
    3. CO@Jeff - By its very nature 'Software Patterns' are very context sensitive and not as universal across programming languages and platforms. Read this http://blog.plover.com/2006/09/11/ . So when discussing software patterns, some level of subjective rationale in inevitable.
      singulars
      1. PODo we need to use the Repository pattern when working in ASP.NET MVC with ORM solutions?
      1. USBikal Lem
 

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