diff options
| author | Xavier Morel <xmo@odoo.com> | 2016-10-26 09:44:37 +0200 |
|---|---|---|
| committer | Xavier Morel <xmo@odoo.com> | 2016-10-26 09:44:37 +0200 |
| commit | 4d60c1f62eaac245ccde70373413a15f33952a0e (patch) | |
| tree | a74850cce619b048c2e39f1b3aaeb892dc4f6b8b /addons/web/static/src/js/framework/pyeval.js | |
| parent | 651738303a06b8c24b0d4334e4a62343884b305b (diff) | |
[FIX] partially revert 3e2e1d6b905c
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.
Diffstat (limited to 'addons/web/static/src/js/framework/pyeval.js')
0 files changed, 0 insertions, 0 deletions