Database schema updates

The database schema is its tables, columns, and relationships. New code may need changes there before deployment. Find the log and required decisions in the schema updates section inside “Database”.

When are changes applied?

When schema updates on deployment are enabled, supported additions are applied automatically before the build. Risky changes, such as removing a column or table, block the step until the owner confirms. Unsupported changes remain blocked. This updates the schema; it does not copy all development rows to production.

Reviewing the log and pending changes

1. 1

   Open schema updates

   After database setup, open “Database” and expand schema updates. Wait for the list to load.

2. 2

   Read each change’s impact

   Applied changes appear with their times. For pending changes, read the summary, potential data loss, and suggested alternative.

3. 3

   Choose cancellation or confirmation

   To preserve the data, cancel and ask Codey to revise the design using the suggested alternative. If you accept the impact, use the confirm-and-apply button as the owner. Confirmation can immediately start applying changes to production.

4. 4

   Wait for the result

   If another risky change remains, the message says your decision was recorded and other changes still await confirmation. Review each one. If application fails, do not assume the schema is complete; read the message and log.

5. 5

   Retry deployment

   After addressing the cause, return to “Deploy” and deploy again. Cancellation alone does not make the new code compatible; Codey needs to remove its dependence on the rejected change.