cubicweb #1625101 sync_schema may fail to update __unique_together__ [rejected]

The unique indexes is not recreated in some conditions:

When you have a relation included in a __unique_together__ and you replace it by a new relation, the sync_schema_props_perms action that is needed to update the __unique_together__ related database indexes must be performed before the old relation is dropped, otherwise the unique indexes is not recreated.

Note that rename_relation migration action probably always fail (I have already experienced this as far as I can remember).

priorityimportant
typebug
done in3.18.7
load0.000
load left0.000
closed by<not specified>