You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upgrade process in Odoo currently has a major issue with how it updates the DB.
Setup:
2 modules: module_parent and module_child
module_child is dependent on module_parent
module_parent has a model: user, with role, not required=False (default).
module_child updates that model: user, with role required=True (explicitly set).
If you update PARENT, the following happens:
Load modules to update
Update module_parent
Update the DB, removing the "not null" requirement from user.role (locking the table!)
Commit the changes???
Update module_child
Update the DB, re-adding the "not null" requirement from user.role
The major issue with this is that it becomes impossible to update modules on a large production environment. Because it's very likely (and actually happening) that:
A: The table lock on user causes issues with other running processes at the same time.
B: There is a period of time where the not null constrained is removed from the DB. If there are many modules to update, this is quite serious!
The text was updated successfully, but these errors were encountered:
The upgrade process in Odoo currently has a major issue with how it updates the DB.
Setup:
user
, withrole
, not required=False (default).user
, withrole
required=True (explicitly set).If you update PARENT, the following happens:
user.role
(locking the table!)user.role
The major issue with this is that it becomes impossible to update modules on a large production environment. Because it's very likely (and actually happening) that:
user
causes issues with other running processes at the same time.The text was updated successfully, but these errors were encountered: