Olivier Laurent 6b55bea979 [FIX] purchase: drop view before creating it ...

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.

closes #14028

2016-10-28 10:54:48 +02:00

..

__init__.py

…

purchase_order_templates.xml

[MIG] purchase: Migrate to new API

2016-08-05 14:04:37 +02:00

purchase_quotation_templates.xml

[MIG] purchase: Migrate to new API

2016-08-05 14:04:37 +02:00

purchase_report_views.xml

[FIX] all: remove external ids fakely from base

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

purchase_report.py

[FIX] purchase: drop view before creating it

2016-10-28 10:54:48 +02:00

purchase_reports.xml

[MIG] purchase: Migrate to new API

2016-08-05 14:04:37 +02:00