From f085a67b745b07572b2a371bca028c227b9369a4 Mon Sep 17 00:00:00 2001 From: Xavier Morel Date: Fri, 19 May 2017 13:43:49 +0200 Subject: [PATCH] [FIX] P3: columns initialisation order is unspecified With P3's hash randomisation, assuming one column is initialised before the other in the same model basically never works. --- addons/project_timesheet_holidays/models/res_company.py | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/addons/project_timesheet_holidays/models/res_company.py b/addons/project_timesheet_holidays/models/res_company.py index 3d21974573c..8dfe3ff580c 100644 --- a/addons/project_timesheet_holidays/models/res_company.py +++ b/addons/project_timesheet_holidays/models/res_company.py @@ -14,11 +14,8 @@ class Company(models.Model): 'project.task', string="Leave Task", domain="[('project_id', '=', leave_timesheet_project_id)]") - def _init_column(self, name): - super(Company, self)._init_column(name) - - if name == 'leave_timesheet_project_id': - self.search([('leave_timesheet_project_id', '=', False)])._create_leave_project_task() + def init(self): + self.search([('leave_timesheet_project_id', '=', False)])._create_leave_project_task() @api.model def create(self, values):