Timeline for Does using the strategy pattern for persistence methods make it "okay" to include CRUD methods in a business object?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2017 at 14:28 | vote | accept | TheCatWhisperer | ||
| Apr 19, 2017 at 15:28 | comment | added | TheCatWhisperer | David, no worries, I was being somewhat facetious. However, I could new an object up, then call the instance Load method by passing it the Id I want and then the object would hydrate itself. | |
| Apr 19, 2017 at 6:51 | history | edited | Andy | CC BY-SA 3.0 |
added 1359 characters in body
|
| Apr 19, 2017 at 6:12 | comment | added | Andy | @TheCatWhisperer I am sorry if it came out that way. That was definitely not the intention. I was trying to state the obvious. Because you had mentioned the CRUD operations, when you want to actually create the business object using a persistence layer it makes no sense to be done through a constructor, then you would have the entity already and would not need the persistence. Hence the mention of a static method. | |
| Apr 18, 2017 at 20:33 | comment | added | TheCatWhisperer | wooooaaaa there! No one said anything about static methods in business objects! Your potty mouth is not appreciated ;) | |
| Apr 18, 2017 at 20:08 | history | answered | Andy | CC BY-SA 3.0 |