Timeline for Representing database tables as objects
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 16, 2022 at 8:42 | comment | added | Doc Brown | Data-centric modeling is not necessarily a bad thing when all you want to create is a simple data management application. Quite the opposite - shoehorning every system into an OO corset can overcomplicate simple tasks. | |
| Nov 16, 2022 at 5:51 | review | Close votes | |||
| Dec 1, 2022 at 3:04 | |||||
| Nov 15, 2022 at 23:00 | comment | added | Flater | I assume you misspoke, but note the difference between representing the table as an object, and representing a single table row as an object. I assume you mean the latter. | |
| Nov 15, 2022 at 22:35 | answer | added | candied_orange | timeline score: 4 | |
| Nov 15, 2022 at 21:49 | comment | added | tntenigma | As well, suppose in the future I want to allow a user to add a business/organization to their address book and relate contacts to specific businesses/organizations. How would I ensure my domain objects are scalable? | |
| Nov 15, 2022 at 21:44 | history | edited | tntenigma | CC BY-SA 4.0 |
deleted 5 characters in body
|
| S Nov 15, 2022 at 21:44 | review | First questions | |||
| Nov 16, 2022 at 0:27 | |||||
| S Nov 15, 2022 at 21:44 | history | asked | tntenigma | CC BY-SA 4.0 |