Timeline for repository pattern, using the domain object as data access object
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2020 at 16:01 | answer | added | Ewan | timeline score: 3 | |
| Jul 8, 2020 at 8:30 | answer | added | Flater | timeline score: 2 | |
| Jul 8, 2020 at 7:43 | comment | added | Flater |
@RobertHarvey: You can actually get around the loss of change tracking if you use interfaces instead of objects, and both the domain object and entity implement the interface. E.g. if I pass a Domain.Foo : IFoo to my DAL (as an IFoo) it gets converted to a DAL.Foo : IFoo, but my DAL returns DAL.Foo (as an IFoo). If I then take something from the DAL and then hand it back to the DAL, it's actually still using the same tracked DAL.Foo object. This does come with some additional mapping logic and requires some extra effort, but it works.
|
|
| Jul 8, 2020 at 0:13 | comment | added | Robert Harvey | The most significant problem you are going to encounter with Entity Framework if you intend to take the hard stance and provide separate objects in another layer is that you are going to lose change tracking. This has an impact on performance and greatly increases the difficulty and complexity of using Entity Framework as a Data Access Layer. | |
| Jul 7, 2020 at 22:26 | history | asked | AgostinoX | CC BY-SA 4.0 |