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.

It's possible for the user to create tables inside the working copy that Kart uses, but if they do so, Kart will never take any notice of them, and there is currently no correct way to add them to the Kart repository (you could try importing such a table, but unless you rename it during import, the imported data will collide with the original table, which will cause the command to fail and add to

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