Why UNIQUE constraint is not updated after it is modified and the module is upgraded (or deactivated/activated)? New constraint is updated only after removing the old constraint.
Because we can not know if the constraint has changed or not (and we can not replace them on each update for performance reason).
OK. Are field types not updated (after they are modified) for the same reason?
No, it updates if there is a lossless way to do it otherwise it shows a warning.
I had to change type Numeric to type Char for a field. The type Numeric for this field remained in the database after the module was updated.
It is normal, it is not a valid transformation.
However, there were no warnings. And I had to manually change the field type in the database.
Sorry. There were warnings in the file warning.log.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.