diff options
| author | Yannick Tivisse <yti@odoo.com> | 2016-09-01 10:25:15 +0200 |
|---|---|---|
| committer | Yannick Tivisse <yti@odoo.com> | 2016-09-02 08:46:33 +0200 |
| commit | 98675d3919b75c9a88247fd5f7e017278f9593a0 (patch) | |
| tree | 0e660d3d4b141f9d13f152bd4b059f9f2a23e975 /addons/theme_default/data/theme_default_data.xml | |
| parent | 07ae5c57eb0a636690bb043729a770e63e62a42f (diff) | |
[IMP] project: Replace 'Cumulative Flow' by a fovorite filter in task report
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
Diffstat (limited to 'addons/theme_default/data/theme_default_data.xml')
0 files changed, 0 insertions, 0 deletions
