Recipes for Continuous Database Integration: Evolutionary Database Development

Recipe 11Integrating on Every Check-In

Problem: When other team members change the database, how do you know whether everything they changed works with existing code?

With other team members changing code and the database, you want to make sure no changes break the existing code. You can find numerous papers and books on CI methods to use with code, but what about database changes? Because the database is linked with the application, you need a way to make sure changes don't break code that could be database code or application code.

Solution

When a developer checks in code changes, they can be tested and integrated with other code changes. When developers change the code and database, however, the integration phase must also take database-level ...