Review a database structure change
Add a column, find who reads that table, collect their decisions.
By the OneEnv team · Last updated
Prerequisites
- A DB Master with a table that at least one service inherits (the database, or the table itself).
- An active branch.
Steps
- Add the column in DB Master. It is staged as a database-column change.
- Optionally view the migration preview for the column to review the generated ALTER TABLE text.
- Submit; an Owner or Admin merges.
- Each service that inherits the database or table covering that column receives a decision. Approve gives it the column. Reject leaves it without.
Removing a column
Staging a removal notifies only services holding a direct membership of that column. Approving removes the column from the service; rejecting keeps the service's membership and does not delete anything.
Reminder
OneEnv records structure; it does not alter your database. Run your own migration, and use the decision trail to know which services agreed.