Data Versioning

One of the most important features in Mycorr is data versioning, which ensures that every significant change to your table is tracked and recoverable. This ensures a robust collaboration and provides the ability to restore previous states of your tables.

Table Versions

Each Table has a Snapshot at any given version. A Table Snapshot holds the Table Version, the Table Meta and the Table Schema at that version.

The Table Meta includes the metadata about rows, and on the other hand, the Table Schema includes the metadata about columns and the overall schema of the table.

Each data operation performed on a table, such as editing the schema, rows or modifying the data itself, results in the creation of a new Table Version. This ensures that you always have a complete history of meaningful changes.

Operations that do not affect the data or schema, such as resizing the table views, do not increment the Table Version.

Checkpoints

You can define a checkpoint for any table version. A checkpoint acts as a restorable point in your table's history.

Each table version can have one checkpoint.

Checkpoints can be deleted at any time.

Aliases

Aliases provide a way to give a table version a human-friendly name. When you rename a checkpoint, you are creating or updating an alias.

You can create many aliases for a Table Version, and you can set one of them as the default name for the Table Version.

Aliases can be deleted at any time.

Restoring and Checking Out

• Owned Tables: If the Table is Owned, meaning that you are working in it's parent Model, you can restore it to any checkpoint, effectively rolling back to that point in history.
• Imported Tables: For tables you have imported from other Models, you can only view a certain checkpoint, not restore or modify the original table.