4 ms·
Breaking database changes do not happen often. There could be multiple solutions to that: 1) Other developers wait. 2) Affected functionality is turned off wh
by dennisgorelik 12y ago
Breaking database changes do not happen often. There could be multiple solutions to that:
1) Other developers wait.
2) Affected functionality is turned off while in transition.
3) Changes implemented in a non-breaking way.
4) Change is done quickly.
5) Separate database environment is setup in order to prepare change.
In any case, the harder problem is to deploy that database change into production when thousands of users are working on it at once.
Practicing that change in development environment helps to make production deployment smoother.
- collyw 12y agoFair enough, I am guessing your work is at a different scale from mine. We are "super agile" (constantly changing) due to the changing nature of the sequencing technology we work with.