You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current version of the script that checks for impossible schema changes does not detect changes to VectorMembers, OneToOneRelations and OneToManyRelations. Instead it just let's schemas with these changes pass without warning or error. The schema evolution mechanism can in principle handle these, but will need some manual intervention obviously. As a first step, we should at least detect these changes and mark them as impossible, instead of letting users run into runtime issues when doing changes like these and trying to read old files.
The text was updated successfully, but these errors were encountered:
The current version of the script that checks for impossible schema changes does not detect changes to
VectorMembers
,OneToOneRelations
andOneToManyRelations
. Instead it just let's schemas with these changes pass without warning or error. The schema evolution mechanism can in principle handle these, but will need some manual intervention obviously. As a first step, we should at least detect these changes and mark them as impossible, instead of letting users run into runtime issues when doing changes like these and trying to read old files.The text was updated successfully, but these errors were encountered: