It can happen that a DB carries old tool/feature/method definitions with the hope that they are useful, but the user may purge and reimport the is_active parameter definitions and boolean value lists their tool/feature/method defs were referring too, in which case they are completely useless. So I suggest we distrust the tool/feature/method for compatibility transformations at commit time, and only trust them for migration purposes (when we know the referential integrity is intact).
It can happen that a DB carries old tool/feature/method definitions with the hope that they are useful, but the user may purge and reimport the is_active parameter definitions and boolean value lists their tool/feature/method defs were referring too, in which case they are completely useless. So I suggest we distrust the tool/feature/method for compatibility transformations at commit time, and only trust them for migration purposes (when we know the referential integrity is intact).