GitLab

[ADD] add_fields: Add a field definition

This method adds all the needed stuff for having a new field populated in
the DB (SQL column, ir.model.fields entry, ir.model.data entry...).

It's intended for being run in pre-migration scripts for pre-populating
fields that are going to be declared later in the module.

NOTE: This only works in >=v8 and is not needed in >=v12, as now Odoo always
add the XML-ID entry:
https://github.com/odoo/odoo/blob/9201f92a4f29a53a014b462469f27b32dca8fc5a/odoo/addons/base/models/ir_model.py#L794-L802

:param: field_spec: List of tuples with the following expected elements
  for each tuple:

  * field name
  * model name
  * SQL table name: Put `False` if the model is already loaded in the
    registry and thus the SQL table name can be obtained that way.
  * field type: binary, boolean, char, date, datetime, float, html, integer,
    many2many, many2one, monetary, one2many, reference, selection, text,
    serialized. The list can vary depending on Odoo version or custom added
    field types.
  * SQL field type: If the field type is custom or it's one of the special
    cases (see below), you need to indicate here the SQL type to use
    (from the valid PostgreSQL types):
    https://www.postgresql.org/docs/9.6/static/datatype.html
  * module name: for adding the XML-ID entry.

Disable filters with invalid context.

[RFC] rename field xmlids when renaming models

disable_invalid_filters: Python 3 compatibility

Fix logging with non-ascii characters in exception.

str() should never be used in Python 2 if you can not know the encoding
of the string.

In this case it can log and raise a UnicodeEncodeError in migration.log
instead of the exception causing the error, and you cannot know why
your migration failed.

I use repr() for Python 2. It's not perfect but the exception is
displayed and the stacktrace is in the log because of logger.exception(),
which is bypassed if str() cause enother exception.

[ADD] disable_invalid_filters

Avoid errors on migrated databases making a non-destructive disabling.

It analyzes all the existing active filters to check if they are still
correct. If not, they are disabled for avoiding errors when clicking on
them, or worse, if they are default filters when opening the model/action.

To be run at the base end-migration script for having a general scope. Only
assured to work on >= v8.

[ADD] delete_template_translations: New method for deleting translations of changed templates with noupdate true (#87)

[ADD] Replace account types in Odoo 9.0

[IMP] rename_fields: Several improvements

For avoiding to rewrite all records (although with no change)

[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