GitLab

[ADD] rename_fields: New method for renaming completely fields

This, in contrast of ``rename_columns``, performs all the steps for
completely rename a field from one name to another. This is needed for
making a complete renaming of a field with all their side features:
translations, filters, exports...

Call this method whenever you are not performing a pure SQL column renaming
for other purposes (preserve a value for example).

This method performs also the SQL column renaming, so only one call is
needed.

[FIX][set_defaults] New api adaptation

[FIX] docstring

[ADD] support update mode where we never try to create records

[RFR] Python 3 compatibility

Added suggestion for latest version install in docs

[FIX] when renaming/deleting a module, rename/delete its xmlid

fixes OCA/OpenUpgrade#934

[FIX] support versions without _fields

[FIX] m2o_to_x2m: Compatible with Odoo v10

* _columns doesn't exist on v10
* _sql_names dissapears also
* On >= 8.0, env is available for getting classes objects

[ADD] protect openerp imports

[FIX] Adapt code to docstring by passing env by default starting from 10.0

[ADD] convert_binary_field_to_attachment

This method converts the 8.0 binary fields to attachments like Odoo 9.0
makes with the new attachment=True attribute. It has to be called on
post-migration script, as there's a call to get the res_name of the
target model, which is not yet loaded on pre-migration.

You need to rename the involved column in pre-migration script if you
don't want to lose your data in the process.

This method also removes after the conversion the source column for
avoiding data duplication.

This is done through Odoo ORM, because there's a lot of logic associated
with guessing MIME type, format and length, file saving in store...
that is doesn't worth to recreate it via SQL as there's not too much
performance problem.

:param env: Odoo environment
:param field_spec: A dictionary with the ORM model name as key, and as
    dictionary values a tuple with:
        * field name to be converted as attachment as first element.
        * SQL column name that contains actual data as second element. If
          the second element is None, then the column name is taken
          calling `get_legacy_name` method, which is the typical technique.

* field name to be converted as attachment as first element.
* SQL column name that contains actual data as second element. If
  the second element is None, then the column name is taken
  calling `get_legacy_name` method.

Leaving untouched the non update ir.model.data entries, there are
problems loading the database when the migration ends, as some
of the related records can be assets, views...

Renaming the entries to an unique name (generated from ID), we
assure Odoo's update process removed them when updating the target
module. If we would remove it them instead, we will need to remove
manually the related resources as well, so this is the best
strategy.

For acknowledge of the need of calling rename_tables also.

[IMP] update_module_names: Add merge option

With these minimal changes, we allow to reallocate all the resources
related to a module that has been merged into others in later
versions. For example, email_template in version 8 that has been
integrated in mail module in version 9.

[FIX] Travis

Due to https://gitlab.com/pycqa/flake8/issues/268, we cannot use
last flake8 version, so we lock it in requirements.txt

unless strictly necessary

In this case, the problem is that installing openupgradelib would
downgrade the wheel package, which is undesirable.