diff options
| author | Martin Trigaux <mat@odoo.com> | 2019-04-01 09:46:56 +0000 |
|---|---|---|
| committer | Raphael Collet <rco@odoo.com> | 2019-04-04 14:41:26 +0000 |
| commit | 489494e733920e4f18e8c86b278166156ff678cf (patch) | |
| tree | 1b2a6be119106b5b4a8455e70de726700b662530 /addons/web/static/src/js/fields/basic_fields.js | |
| parent | 112bd835d80619a0337dca10b21aa6ca68e3303d (diff) | |
[FIX] base: upsert translations during copy_translations
When doing a copy, create the new translations directly in SQL and handle
potential conflicts.
Conflicts can occure in case of reinstallation as showed in opw-1955062 and
opw-1950117.
In case of "leftovers" of translations (e.g. remaining after the uninstallation
of a module), creating the new translations (when reinstalling the module) may
produce a conflict with (type, name, res_id, lang) and raise an error.
This is NOT a problem of reading .po file during installation (which handles
correctly conflicts) but of business code creating new records and linked
translations (e.g. website copying website.menu records).
Removing old translations during uninstall is handled in a previous commit in
ir.model.fields _drop_column method.
This commit fixes the reinstallation on instances with leftover translations
and fixes the issue without needing a manual intervention (i.e. delete the old
translations manually).
Closes odoo/odoo#32056
Signed-off-by: Raphael Collet (rco) <rco@openerp.com>
Diffstat (limited to 'addons/web/static/src/js/fields/basic_fields.js')
0 files changed, 0 insertions, 0 deletions