Is this behaviour changing with the forthcoming RDB loader changes?
It is. Migration would be performed up the latest version in batch.
Because in future it will be completely valid for a table ...
This release is used to assess migration from old to new loader.
I found that a lot of migration (from static generate) errors were caused by the VARCHAR sizes. So data would be loading (truncated) into the correct table. After the patch it would end up in the a recovery table, which would be unexpected for the users.
After most of the users are migrated away it would be fair to remove this check or make it warning. But at this moment it has a purpose.
It is. Migration would be performed up the latest version in batch.
This release is used to assess migration from old to new loader.
I found that a lot of migration (from
static generate) errors were caused by the VARCHAR sizes. So data would be loading (truncated) into the correct table. After the patch it would end up in the a recovery table, which would be unexpected for the users.After most of the users are migrated away it would be fair to remove this check or make it warning. But at this moment it has a purpose.