Data Versioning

Every change to a table's rows or columns creates a new version. Mycorr keeps them, so you can go back to an earlier state, compare two points in time, and decide which state other people see.

Changes that don't touch data, such as moving or resizing a table on the canvas, don't create a version.

There are three ideas to know:

  • A checkpoint is a version you named so you can come back to it.
  • A release is the checkpoint you publish. It is what everyone outside your model reads.
  • Latest is the current state, which only people working in the model see.

Checkpoints

A checkpoint keeps one version of a table so you can restore, compare or release it later. Each version can have one checkpoint.

To make one, open the table's Checkpoints and click New checkpoint, then give it a name. Anyone who can edit the table can create checkpoints.

From a checkpoint's menu you can:

  • Restore this checkpoint: bring the table back to that state. The restore is itself a new version, so nothing in between is lost.
  • Compare: see the rows added, removed and edited between two checkpoints. An edited row shows as one row gone and one added.
  • View the table at this point, Rename or Delete it.

Aliases

A checkpoint can carry several names, called aliases, and one of them is its default name. Renaming a checkpoint adds an alias. Search by name or alias finds a checkpoint by any of them.

Releases

A release is the version of a table that people outside its model get. When you share a table, or someone imports it into another model, they read the release, never your work in progress.

This lets you keep editing freely: a half-finished change never reaches anyone else until you release it.

  • Set as release (from the table's menu) releases the current version. Release checkpoint releases an older one.
  • A table has one release at a time. Releasing again replaces it, and earlier releases stay in the history marked Released.
  • Unrelease takes the release away.
  • Compare released with current shows what has changed since the release.

Anyone who can edit the table can release it. Catalog tables are released through their dataset instead.

Sharing a table needs a release. If a table has none, the share dialog offers Add a release first. See Sharing Tables.

Imported tables

When you import a table into another model, your model reads the release it was given and stays on it. New edits in the original never change your numbers behind your back.

  • The table's history shows Releases instead of checkpoints. In use marks the release your model reads.
  • When the owner publishes a newer release, Sync to latest release appears on the table. Anyone who can edit your model can take it.
  • You can't restore or change an imported table. Its history belongs to its owner.

AI assistants

The same rule applies through the MCP server: if you can edit a table you read its latest version, and otherwise you read its release. A table with no release can only be read by people who can open its model.