Openupgrade Framework (openupgrade_framework)

Security findings

Migration considerations

Raw `cr.execute()` INSERT/UPDATE/DELETE bypasses the ORM (no compute/constrains/tracking/mail): `UPDATE ir_model_fields SET translate=NULL where translate::varchar='false'` - re-check the table/column names still match after upgrading. migration-raw-sql-write · source
Raw `cr.execute()` INSERT/UPDATE/DELETE bypasses the ORM (no compute/constrains/tracking/mail): `UPDATE ir_module_module SET demo = false` - re-check the table/column names still match after upgrading. migration-raw-sql-write · source

Migration review checklist, not a compatibility verdict. No target version is selected: apply version-specific advice only when migrating to that version or later.

Repository: OCA/OpenUpgrade · module folder · Try on Runboat
Module version: 1.0.0
Category: Migration
Folder size: 0.08 MB
License: AGPL-3
Application: No
Auto-installable: No
Website: https://github.com/OCA/OpenUpgrade
Last tracking update: 2026-10-04 00:16:28
Authors: Odoo Community Association (OCA), Therp BV, GRAP, Opener B.V., Hunki Enterprises BV
Maintainers: Odoo Community Association (OCA), Therp BV, GRAP, Opener B.V., Hunki Enterprises BV
Committers: Holger Brunn, Miquel Raïch, OCA-git-bot

Odoo dependencies

odoo/odoo:

- base

Python dependencies

openupgradelib

System dependencies

None

Required by

None

Description

This module is a technical module that contains a number of
monkeypatches to improve the behaviour of Odoo when migrating your
database using the OpenUpgrade migration scripts:

- Prevent dropping columns or tables in the database when fields or
  models are obsoleted in the Odoo data model of the target release.
  After the migration, you can review and delete unused database tables
  and columns using database_cleanup. See
  <https://odoo-community.org/shop/product/database-cleanup-918>
- When data records are deleted during the migration (such as views or
  other system records), this is done in a secure mode. If the deletion
  fails because of some unforeseen dependency, the deletion will be
  cancelled and a message is logged, after which the migration
  continues.
- Prevent a number of log messages that do not apply when using
  OpenUpgrade.
- Suppress log messages about failed view validation, which are to be
  expected during a migration.
- Run migration scripts for modules that are installed as new
  dependencies of upgraded modules (when there are such scripts for
  those particular modules)
- Production databases generated with demo data, will be transformed to
  non-demo ones. If you want to avoid that, you have to pass through the
  environment variable OPENUPGRADE_USE_DEMO, the value "yes".

For detailed documentation see:

- <https://github.com/OCA/OpenUpgrade/>
- <https://oca.github.io/OpenUpgrade>

Code Analysis info_outline

Views touched (0)

No views found for this module.

HTTP endpoints (0)

No HTTP endpoints found for this module.

Models touched (0)

No models found for this module.

Loading…