Timeline for How to version control shared database?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2020 at 17:18 | comment | added | simbo1905 | you can use git submodules to "mount" the application repos into folders within the main repo. git-scm.com/docs/git-submodule many teams try not to use submodules as with a well-factored architecture you don't need them. when you have the architecture you describe then it might be a good solution. | |
| May 6, 2020 at 11:04 | comment | added | chupasaurus | You can replace "stored procedures" with "data" and it will almost resolve your problem because you'll need more steps to be able to roll back app-specific changes and integrate them in shared procedures, the process would be add app-specific columns/tables and stop using dependent shared procedures in that app → propose the changes in shared data → alter shared data and procedures. In microservice approach each service has it's own database and none of them share original data (e.g. service for accounting should store names in Users table while auth service doesn't need them). | |
| May 6, 2020 at 10:17 | comment | added | Zikato | My problem is I want to recreate an empty database from version control. How to do that if it's split into multiple repos? Which repo should contain the DDL to create tables when they are shared. How to keep the repos in sync with the correct version of DB - especially when branching. | |
| May 5, 2020 at 14:45 | history | answered | chupasaurus | CC BY-SA 4.0 |