Timeline for When Business Object fields should not exactly reflect database columns
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 13, 2012 at 17:53 | answer | added | Nazar Merza | timeline score: 1 | |
May 13, 2012 at 17:20 | vote | accept | Mik378 | ||
May 13, 2012 at 15:29 | comment | added | NoChance | You need to set a policy regarding data access. Either you follow the OO approach or the table-based (store) approach.The capabilities of your ORM and GUI binding options may affect your decision significantly. The Object-Relational impedance mismatch may be a good read: agiledata.org/essays/mappingObjects.html#ShadowData and agiledata.org/essays/impedanceMismatch.html | |
May 13, 2012 at 15:23 | history | edited | gnat | CC BY-SA 3.0 |
minor typo corrected
|
May 13, 2012 at 15:12 | answer | added | lorus | timeline score: 6 | |
May 13, 2012 at 11:46 | answer | added | LinuxMonkey | timeline score: -2 | |
May 13, 2012 at 11:43 | comment | added | Mik378 | I talk about class->table mismatch | |
May 13, 2012 at 11:23 | comment | added | leonigmig | are you just talking about mapping attribute->column names or is there some class->table mismatch? | |
May 13, 2012 at 11:16 | history | asked | Mik378 | CC BY-SA 3.0 |