There is no reason not to support sql_catalog_raise_error_on_uid_check for both cases of UID inconsistency. UID change happens for example with inconsistent catalog and ZODB after disaster recovery. It can be useful to prevent raise during a double catalogin of the database after a disaster recovery. Else, it is just impossible to recover.