Timeline for What's best practice when putting an abstraction layer over an ORM?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2015 at 11:35 | answer | added | Lyise | timeline score: 1 | |
| Sep 11, 2015 at 7:53 | comment | added | Neil | I usually go with the 3rd option, with cross-calling so that all reads of say User eventually call a single method GetUsers with filters, so that yes, you have lots of methods, but small methods and no repeated code. Also I make a point to make GetUsers private so you can't bypass the other methods, allowing you to change the signature later without much trouble. | |
| Sep 11, 2015 at 5:19 | answer | added | Esben Skov Pedersen | timeline score: 1 | |
| Sep 10, 2015 at 22:13 | comment | added | Eric King | My take on why EF (and other ORMs) are not repositories. | |
| Sep 10, 2015 at 21:43 | answer | added | Ewan | timeline score: 2 | |
| Sep 10, 2015 at 21:32 | review | Suggested edits | |||
| Sep 11, 2015 at 0:25 | |||||
| Sep 10, 2015 at 21:12 | answer | added | aaron | timeline score: 1 | |
| Sep 8, 2015 at 8:40 | history | tweeted | twitter.com/#!/StackProgrammer/status/641169320802930688 | ||
| Sep 7, 2015 at 12:06 | comment | added | Euphoric | I take 5th option : Use Repository provided by ORM. | |
| Sep 7, 2015 at 10:26 | comment | added | Michael Obi | On the project I'm working on right now, I'm using the 3rd option. Working fine. | |
| Sep 7, 2015 at 9:28 | history | asked | Bob Tway | CC BY-SA 3.0 |