Timeline for Graph database keeping historical relationships
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Jun 29, 2016 at 17:40 | comment | added | candied_orange | Be careful with square one. Of all the places it can lead it tends to most often lead one of two places: the exact same mess or an even bigger mess. It's easy to look at a failing project and focus only on what's wrong. A lot of work has been done at this point. Spend some time figuring out what isn't broken, or you'll find out when you break that too. | |
| Jun 29, 2016 at 17:01 | comment | added | candied_orange | Many things can't be done. What people really want usually can be done, if you understand it. I submit that you haven't made the requirements clear. What is a "monthly history of the past 5 years" if "history cannot be isolated"? Are you sure these are the same requirement? | |
| Jun 29, 2016 at 16:56 | history | edited | candied_orange | CC BY-SA 3.0 | added 480 characters in body |
| Jun 29, 2016 at 14:14 | comment | added | Henrique Barcelos | Yeah, that's our first thought, but the business analysts state that the history cannot be isolated from each oter, since the state on Jul'16 affects the state in Aug'16, Sep'16 and so on. I am inclined to declare that this can't be done. Our rough calculations show that this database would contain 116 GiB of data per month. | |
| Jun 28, 2016 at 15:34 | history | answered | candied_orange | CC BY-SA 3.0 |