data-versioning

Consider the following table:

dsimple> create table t(val char(3));
dsimple> insert into t values ('dasdsa');
string is too large for column

Dolt should add to the error message the name of the offending column like mysql

mysql> insert into t values ('dasdsa');
ERROR 1406 (22001): Data too long for column 'val' at row 1

On more advanced versions of LakeFS (probably > = v1.0.0), we would like to remove the logic that tries to fill the generation field in DB when loading old dumps. It means we will no longer support loading dump that made with a version lower than v0.61.0.

If you delete a layer in the working copy, then you should be able to commit this to delete the layer in your repo.

If you add a layer to a working copy, then you should be able to commit this to add the layer to your repo.
This is a bit trickier: the layer will need to be modified to have the triggers added etc.

While API action names have been renamed to refer to tag, there are some cases where parameter names and returned struct keys still refer to version.

Examples:

• in resource_show_tag: version_id parameter, version_metadata in the returned dict
• Same in package_show_tag