Timeline for What is the traditional way to maintain extensibility in a database-driven application like this?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2014 at 13:52 | comment | added | Jsess | You're right, adding data won't cause me problems on the coding end - it's just new lines for the table. The problem is that I don't want to have to go back and handle new rows every time a new items is released every other week - I want this single release to stand on its own unless new categories of items are released in new slots (where I can go in and add a brand new tab/handling for this, as this will be far more complex and may need new fields that previous items didn't.) Thank you for the former question, checking it out now! | |
| Mar 23, 2014 at 10:38 | answer | added | david.pfx | timeline score: 1 | |
| Mar 23, 2014 at 7:40 | comment | added | Doc Brown | Can you give an example for where you see problems arising? Adding items to a database row from time to time is nothing which implies a loss in maintainability. And if you mean how to handle database schema changes over time, I recommend this former question: programmers.stackexchange.com/questions/202541/… | |
| Mar 23, 2014 at 7:01 | comment | added | Euphoric | Do you mean new items or new types of items? | |
| Mar 23, 2014 at 1:50 | history | asked | Jsess | CC BY-SA 3.0 |