EddytorDocs & API
07 · Tables A→ZA · Before you start

The stable table UUID

Why metaData.id is a table's permanent identity, and where you'll see it.

Every Delta table has a stable UUID - the metaData.id field in the Delta protocol. Eddytor uses it as the table's permanent identity, and it shows up in a few places worth recognising.

Identity that survives rename/move

A table's fully-qualified name can change - you rename or move it - but its UUID does not. Rename and move copy the underlying _delta_log and data files, so the table keeps the same table_id while its path/FQN changes.

Good to know

Practical consequence: after a rename or move, refresh the FQN from list_tables before further calls - the path changed, the identity didn't.

Where you'll see it

  • In the MCP table string, as the prefix on the table component: eddytor.cfg_abc123.<uuid>_demo_products.
  • As table_id in list_tables output and as the argument to resolve_table, which looks up a table's current location/identity by id.

Resolve by id

When you have a table_id but not the current FQN (e.g. after a move), resolve it:

resolve_table(table_id="abc123…")

Next

On this page