Inventory every reference to the mutable customer code
A customer rename updates its main row but leaves case and attachment references pointing to the old code.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Schema analysis · Referential integrity
Estimated field mix
- Database engineering70%
- System design30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional support platform stores a mutable external account code as its primary relationship key. Renames and imports now break references in several tables.
Setup prerequisites
- Create a disposable database with synthetic customers and dependent records.
- Apply real migration files; never use production db push.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List database foreign keys and application lookup boundaries.
- Classify direct, denormalized and external references.
- Record unresolved references before migration design.
Implementation constraints
- Use repository search and catalog queries against synthetic schema.
Verification to include
- Trace a customer through cases and attachments.
- Add one hidden denormalized fixture reference and ensure the inventory method finds it.
Deliverables
- Reference inventory and discovery queries
Rollout and recovery
Review the inventory before migration; keep unknown dependencies as explicit blockers.
Value of the work
For the engineer: Practice migration ordering, compatibility and referential integrity.
For the team: Review a reversible schema transition with measurable completeness checks.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.