Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 7
    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. Commented Feb 21, 2016 at 21:13
  • 1
    You change the database schema in a way that doesn't lose data, en.wikipedia.org/wiki/Schema_migration . Commented Feb 21, 2016 at 21:18
  • 1
    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/… Commented Feb 21, 2016 at 22:30
  • 1
    "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. Commented Feb 22, 2016 at 13:01