Yannick Tivisse
98675d3919
This report is too advanced and/or complex to be a single menuitem. Furthermore the model was a mess and a horn of plenty for bugs. The class ProjectTaskHistoryCumulative inherits from the class ProjectTaskHistory, and create a view based on the same model.The orginal class defines a compute field 'end_date' which calls a compute method '_compute_end_date' that will either make a simple assignment or a SQL request if the columns is always opened or folded. As ProjectTaskHistoryCumulative is declare with '_auto=False' the compute method will try to write on this table, which is obviously wrong because we are trying to write on a view. This leads to erors when trying to edit a project stage like: OperationalError: cannot update view "project_task_history_cumulative" DETAIL: Views that do not select from a single table or view are not automatically updatable. HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. or when trying to delete a column which already contains some tasks. So we removed this these models and view and replaced them by a simple favorite filter in the Tasks Reports
455 B
455 B
| 1 | id | name | model_id:id | group_id:id | perm_read | perm_write | perm_create | perm_unlink |
|---|---|---|---|---|---|---|---|---|
| 2 | access_project_task_sale_user | project.task salesman | project.model_project_task | sales_team.group_sale_salesman | 1 | 1 | 1 | 1 |
| 3 | access_project_task_type_sale_user | project.task.type salesman | project.model_project_task_type | sales_team.group_sale_salesman | 1 | 0 | 0 | 0 |
| 4 | access_project_project_sale_user | project.project salesman | project.model_project_project | sales_team.group_sale_salesman | 1 | 0 | 0 | 0 |