Actions
Bug #23836
closedEvent log migration should not be done every time
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Fixed
Regression:
No
Description
Currently the database migration to update null values and add constraints to the nullable columns is run every time at startup. We want to run them only if we have not already done the migration : if the column is still nullable.
Also, in case of an error, the log should incite the user to send the details of the error for us to resolve it later.
Actions