Timeline for answer to Relational databases and iterative development by Jan Hudec
Current License: CC BY-SA 3.0
Post Revisions
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Oct 4, 2016 at 8:38 | comment | added | Gordon Wrigley | We're an Agile shop and we run a 100% uptime service and both of those apply to the DB as well. We migrate the production schema on average once a day and I would second everything Jan has said. One additional thing we do that has been invaluable is what we call migration testing, this runs as part of our build and deploy process. It takes a schema snapshot off production, applies any pending migrations from master to it and then runs the unit tests from the currently deployed production code against that schema. The goal is to check that applying the migrations won't break the running system. | |
| Mar 3, 2016 at 10:03 | comment | added | Murphy | Thumbs up for Alex' article; it may not be shorter, but it makes a much more practice-oriented and entertaining read. | |
| Feb 22, 2016 at 16:15 | history | edited | Jan Hudec | CC BY-SA 3.0 |
mention installation by running all the scripts; add WP link to more tools
|
| Feb 22, 2016 at 14:43 | comment | added | Murph | @Tibo you build the schema from scratch by running the same sequence of scripts. That's how you manage the problem. Given that as a standard you can get from any instance of the database - including one that doesn't exist yet - to a current schema and have confidence that its the same. There is no need to have two ways as per your example. (At least not given a consistent baseline - the first step is to establish the baseline and once you get to that baseline the problem goes away.) | |
| Feb 22, 2016 at 12:50 | history | edited | Jan Hudec | CC BY-SA 3.0 |
added 40 characters in body
|
| Feb 22, 2016 at 12:40 | history | edited | Jan Hudec | CC BY-SA 3.0 |
mention using the scripts on test and QA
|
| Feb 22, 2016 at 10:30 | history | answered | Jan Hudec | CC BY-SA 3.0 |