Timeline for Is it fair to call a database or a document a "Model", as in Model/View/Controller?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2013 at 11:22 | answer | added | Red | timeline score: 2 | |
| Aug 4, 2013 at 20:25 | answer | added | Mark Brackett | timeline score: 1 | |
| Aug 4, 2013 at 18:08 | vote | accept | DougM | ||
| Aug 4, 2013 at 18:01 | answer | added | Loki Astari | timeline score: 2 | |
| Aug 3, 2013 at 22:09 | comment | added | DougM | "usually", "just" -- I'm not asking "is the model always just the data." I'm asking "is it fair to just call the data the model, and not bother building a pointless intermediate layer"? (And more importantly, WHY isn't it fair?) | |
| Aug 3, 2013 at 20:17 | comment | added | Marjan Venema | No, a model is much more than "just" the data (even with triggers an all). The model usually uses a data layer to talk to the storage mechanism which may not even be a database. Also MVC is a very specific pattern for UI separation but separation of UI and business logic can be achieved in more ways than MVC. So yes, calling separation of UI and business logic MVC is absolutely unfair if you are not actually following the MVC pattern. Call it what it is: the database or the document, or in more generic terms: the storage. | |
| Aug 3, 2013 at 19:08 | history | asked | DougM | CC BY-SA 3.0 |