Xavier Morel 4d60c1f62e [FIX] partially revert 3e2e1d6b90 ...

One of the behavioural divergences between "create or replace" view and
DROP; CREATE turns out to be that "create or replace" can only add
columns *at the end* of the view, and can not change the name or type of
the view during replacement, which can break migrations.

Reinstate the old drop;create as replacement is not necessary for this
specific view.

2016-10-26 09:44:37 +02:00

..

__init__.py

[REF] crm: lead report and opportunity reports merged, into a single report

2015-07-30 10:19:14 +02:00

crm_activity_report_views.xml

[FIX] all: remove external ids fakely from base

2016-09-02 16:14:26 +02:00

crm_activity_report.py

[FIX] crm: drop (sql) view before recreating it

2016-08-04 19:47:05 +02:00

crm_opportunity_report_views.xml

[FIX] all: remove external ids fakely from base

2016-09-02 16:14:26 +02:00

crm_opportunity_report.py

[FIX] partially revert 3e2e1d6b90

2016-10-26 09:44:37 +02:00