Renaming a column is the refactor every dictionary needs and nobody dares: the name is in SQL, in scripts, in expressions, in layouts. This release makes it a four-step procedure with a human at the one step that writes.
The steps
- Analyse Read-only, with a length-prefixed digest of the plan and a confidence decided per row.
- Prove JavaScript bodies are rewritten by lexing, never by regular expression, so comments and regex literals are untouched: 258 occurrences in 36 bodies, references down from 484 to 73. SQL bodies are rewritten under a differential prepare gate: four repaired, two rewritten, none rejected.
- Apply with a token Apply runs only with a token derived from the plan digest that a person types. The approval tables that preceded it were dropped.
- Verify The lifecycle is migrate, repair, verify, and verify closes the rename. An add strategy keeps the old column for older builds.
Used at scale
- A campaign of 64 renames across six families, and a rename tool that reaches every layer of a dictionary stack.
The token is the design. A machine can plan a rename across thousands of objects; a person decides it happens.