Timeline for Relational databases and iterative development
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2016 at 17:50 | answer | added | theMayer | timeline score: 1 | |
| Feb 22, 2016 at 13:01 | comment | added | Bent | "Apart from that, even if we try to get a perfect model upfront, which I'm already convinced is very hard, requirements may change." I would like to add that you should not even try to get a (close to perfect) model up front. That might tie your mindset down to one type of solutions instead of keeping your options open. | |
| Feb 22, 2016 at 10:30 | answer | added | Jan Hudec | timeline score: 16 | |
| Feb 22, 2016 at 10:07 | answer | added | gbjbaanb | timeline score: -1 | |
| Feb 22, 2016 at 7:20 | history | tweeted | twitter.com/StackProgrammer/status/701667767016103936 | ||
| Feb 21, 2016 at 22:30 | comment | added | Doc Brown | I am sure this topic was extensively discussed somewhere before, just can't find it on Programmers. But see here martinfowler.com/articles/evodb.html or here stackoverflow.com/questions/334059/… | |
| Feb 21, 2016 at 21:18 | comment | added | RemcoGerlich | You change the database schema in a way that doesn't lose data, en.wikipedia.org/wiki/Schema_migration . | |
| Feb 21, 2016 at 21:13 | comment | added | Ixrec | Incidentally, I don't think this has anything to do with relational databases in particular. I have a similar problem with a project I'm working on, but we're having it with the schema for our JSON strings that represent very non-relational objects. It probably affects all forms of persistence equally. | |
| Feb 21, 2016 at 20:12 | history | edited | user1620696 | CC BY-SA 3.0 |
deleted 49 characters in body
|
| Feb 21, 2016 at 20:05 | history | asked | user1620696 | CC BY-SA 3.0 |