Timeline for Why shouldn't I use the repository pattern with Entity Framework?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 25 at 21:57 | comment | added | Basilevs | How is it redundant, when EF tightly couples your model to DAL? | |
| Jan 21, 2016 at 10:24 | comment | added | ColacX | this is what he meant. var id = Entity.Where(i => i.Id == 1337).Single() encapsulated and wrap this in a repository you basically cannot do query logic like this from the outside, which either forces you to A add more code to the repository and the interface for fetching id. B return the entity context from the repository so that you can write the query logic (which is just nonsense) | |
| Oct 29, 2015 at 15:44 | comment | added | ManirajSS | could you please tell some of the advantages for "Entity Framework gives you a wealth of coding and functional advantages"? | |
| Mar 20, 2013 at 17:22 | review | First posts | |||
| Mar 20, 2013 at 17:29 | |||||
| Mar 20, 2013 at 17:05 | history | answered | Russell Horwood | CC BY-SA 3.0 |