Timeline for Who communicates with the database in MVC/MVP?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2017 at 14:01 | comment | added | user3629892 | So in an application that uses hibernate, MySQL and a DAOLayer, the classes that represent the database tables and have @Entity annotations are just PART of the model but they don't solely make up the model? | |
| Feb 23, 2016 at 12:05 | comment | added | zaitsman | Good answer. Important to note that having everything with badly implemented DDD in mind results in fat models that are very hard to modify. Personally i prefer a simple model with a bunch of properties and no methods and then the service layer to do modifications and ORM (or whatever class you use for that, CoreData etc) to do actual connecting to the db and saving. | |
| Feb 23, 2016 at 1:53 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 3 characters in body
|
| Feb 23, 2016 at 1:41 | comment | added | Luca Fülbier | Very nice explanation, thank you! I should probably buy Fowlers book in the future, i keep coming back to his articles a lot lately ;-) | |
| Feb 23, 2016 at 1:39 | vote | accept | Luca Fülbier | ||
| Feb 23, 2016 at 1:34 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 256 characters in body
|
| Feb 23, 2016 at 1:20 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 179 characters in body
|
| Feb 23, 2016 at 1:13 | history | answered | Robert Harvey | CC BY-SA 3.0 |