Skip to content

Standard Skill: Schema Change Fix

Schema Change Fix is a Standard Skill: it brings the Semantic Layer of a Data Source back in line with its schema after the Schema Watcher noticed a change. Fix with agent on a schema notice opens a Conversation with it, and the agent also loads it when you say a table or column was renamed, added, removed or retyped. To pick it yourself, type / and choose schema-change-fix.

  1. It reads what the Semantic Layer says: the Data Model, and every Verified Query, Rule, Term and Benchmark that names a changed table or column. If none does, it says there is nothing to fix and may offer to draft a Data Model.
  2. It confirms the change in the database, as the schema is now, not only as the notice describes it, because it may have changed again. A column removed and another added with a similar name or the same type is likely a rename: it checks that with one counting query and says how sure it is.
  3. It decides the fix: a rename changes every reference, in the Data Model and in the SQL of Verified Queries; a removed column or table leaves the Data Model, and it says what replaces anything that needed it; an added column goes into the Data Model only if it matters for the questions people ask; a changed type is changed where the model states it. What it can’t settle from the data, it asks you, one question at a time.
  4. It proposes the whole fix as one Context Change Request, whose explanation names the schema change, what each entry now says, what it left out and any open question.

The Right to create Context Change Requests on the Data Source. Without it, the agent tells you that someone who holds it can use Fix with agent, and stops. Nothing changes until someone who may accept Context Change Requests on the Data Source accepts the request.