OpenUpgrade API¶
The OpenUpgrade library contains all kinds of helper functions for your pre and post scripts, in OpenUpgrade itself or in the migration scripts of your own module (in either major or minor version upgrades). It can be installed with
-pip install openupgradelib
+pip install openupgradelib
and then used in your scripts as
from openupgradelib import openupgrade
-
+
General methods¶
-
@@ -61,7 +59,7 @@
OpenUpgrade API
-- Param
+- Param:
field_spec: List of tuples with the following expected elements
for each tuple:
@@ -95,7 +93,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
columnspec – tuple of (column name, column type)
@@ -162,7 +160,7 @@ OpenUpgrade API
-Parameters
+Parameters:
model_name – Name of the model.
origin_field_name – Name of the field from which the values
@@ -182,7 +180,7 @@
OpenUpgrade APIopenupgradelib.openupgrade.copy_columns(cr, column_spec)¶
Copy table columns. Typically called in the pre script.
-- Parameters
+- Parameters:
column_spec – a hash with table keys, with lists of tuples as
values. Tuples consist of (old_name, new_name, type). Use None for
new_name to trigger a conversion of old_name using get_legacy_name()
@@ -201,7 +199,7 @@
OpenUpgrade APIopenupgradelib.openupgrade.copy_fields_multilang(cr, destination_model, destination_table, destination_columns, relation_column, source_model=None, source_table=None, source_columns=None, translations_only=False)¶
Copy field contents including translations.
-- Parameters
+- Parameters:
destination_model (str) – Name of the destination model where the data will be copied to.
destination_table (str) – Name of the destination table where the data will be copied to.
@@ -281,7 +279,7 @@
OpenUpgrade API
-- Parameters
+- Parameters:
model – the model for which workflow transitions should be deactivated
transitions – a list of (‘module’, ‘name’) xmlid tuples of transitions to be deactivated. Don’t pass this if there’s no specific reason to do so, the default is to deactivate all transitions
OpenUpgrade API
-- Parameters
+- Parameters:
cr – DB cursor.
model (str) – Model name.
OpenUpgrade APIopenupgradelib.openupgrade.delete_record_translations(cr, module, xml_ids)¶
Cleanup translations of specific records in a module.
-- Parameters
+- Parameters:
module – module name
xml_ids – a tuple or list of xml record IDs
OpenUpgrade API
-- Parameters
+- Parameters:
xml_ids – List of XML-ID string identifiers of the records to remove.
delete_childs – If true, also child ids of the given xml_ids will
@@ -363,7 +361,7 @@
OpenUpgrade API
-- Parameters
+- Parameters:
env – Environment parameter.
@@ -377,7 +375,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
column_spec – a list of (table, column) tuples
@@ -389,7 +387,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
table – The table
field – The field name for which we want to change the type
OpenUpgrade API
-- Parameters
+- Parameters:
original_name – the original name of the column
version – current version as passed to migrate()
OpenUpgrade API
-- Parameters
+- Parameters:
module_name – the name of the module
filename – the path to the filename, relative to the module directory. This may also be the module directory relative to –upgrade-path
OpenUpgrade APIopenupgradelib.openupgrade.logged_query(cr, query, args=None, skip_no_result=False)¶
Logs query and affected rows at level DEBUG.
-- Parameters
+- Parameters:
query – a query string suitable to pass to cursor.execute()
args – a list, tuple or dictionary passed as substitution values
@@ -488,7 +486,7 @@
OpenUpgrade API
-- Parameters
+- Parameters:
args_details – if True, arguments details are given in the log
step – The log will be done only every step times.
OpenUpgrade API
-- Parameters
+- Parameters:
model – The target model registry object
table – The source table
OpenUpgrade API
-- Parameters
+- Parameters:
cr – The database cursor
source_column – the database column that contains old values to be mapped
OpenUpgrade API
-- Parameters
+- Parameters:
module – the module name that the message concerns
table – the model that this message concerns (may be False, but preferably not if ‘column’ is defined)
OpenUpgrade API
-- Parameters
+- Parameters:
transition_conditions – a dictionary returned by deactivate_workflow_transitions
@@ -672,7 +670,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
tables ([str, ...]) – List of tables where the FKs were declared, and where they will be
removed too. If a table doesn’t exist, it is skipped.
OpenUpgrade APIopenupgradelib.openupgrade.rename_columns(cr, column_spec)¶
Rename table columns. Typically called in the pre script.
-- Parameters
+- Parameters:
column_spec – a hash with table keys, with lists of tuples as values. Tuples consist of (old_name, new_name). Use None for new_name to trigger a conversion of old_name using get_legacy_name()
@@ -705,7 +703,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
env – Environment/pool variable. The database cursor is the only
thing needed, but added in prevision of TODO tasks for not breaking
@@ -748,7 +746,7 @@
OpenUpgrade API
-- Parameters
+- Parameters:
table_spec – a list of tuples (old table name, new table name). Use None for new_name to trigger a conversion of old_name to the result of get_legacy_name()
@@ -762,7 +760,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
xmlids_spec – a list of tuples (old module.xmlid, new module.xmlid).
allow_merge – if the new ID already exists, try to merge the records.
@@ -784,7 +782,7 @@
OpenUpgrade API
-- Parameters
+- Parameters:
records – an iterable (not necessarily recordset) of records to
unlink.
OpenUpgrade API
-- Parameters
+- Parameters:
pool – you can pass ‘env’ as well.
default_spec – a hash with model names as keys. Values are lists of tuples (field, value). None as a value has a special meaning: it assigns the default value. If this value is provided by a function, the function is called as the user that created the resource.
OpenUpgrade APIopenupgradelib.openupgrade.set_xml_ids_noupdate_value(env, module, xml_ids, value)¶
Set the xml_ids noupdate values in a module.
-- Parameters
+- Parameters:
module – module name
xml_ids – a tuple or list of xml record IDs
OpenUpgrade APIopenupgradelib.openupgrade.update_field_multilang(records, field, method)¶
Update a field in all available languages in the database.
-- Parameters
+- Parameters:
records – Recordset to be updated.
field (str) – Field to be updated.
OpenUpgrade API
-- Parameters
+- Parameters:
cr – Database cursor
model – model name
OpenUpgrade API
-- Parameters
+- Parameters:
namespec – list of tuples of (old name, new name)
merge_modules – Specify if the operation should be a merge instead
@@ -907,11 +905,11 @@
OpenUpgrade API
-- Parameters
+- Parameters:
ref_spec_actions – list of tuples with couple of workflow.action’s
external ids. The first id is replaced with the second.
- Returns
+- Returns:
None
@@ -930,7 +928,7 @@ OpenUpgrade API
-- Parameters
+- Parameters:
old_module – name of the old module
fields – list of dictionary with the following keys:
@@ -945,8 +943,8 @@
OpenUpgrade API
+
+
Methods for OpenUpgrade 7.0¶
The following specific methods for 7.0 are available. These have been
developed to cover specific needs as per data model changes in that
@@ -963,7 +961,7 @@
Methods for OpenUpgrade 7.0openupgradelib.openupgrade_70.set_partner_id_from_partner_address_id(cr, pool, model_name, partner_field, address_field, table=None)¶
Set the new partner_id on any table with migrated contact ids
-- Parameters
+- Parameters:
model_name – the model name of the target table
partner_field – the column in the target model’s table that will store the new partner when found
Methods for OpenUpgrade 7.0Returns
+- Returns:
nothing
-
+
+
Methods for OpenUpgrade 8.0¶
The following specific methods for 8.0 are available. These have been
developed to cover specific needs as per data model changes in that
@@ -990,7 +988,7 @@
Methods for OpenUpgrade 8.0
-Parameters
+Parameters:
cr – database cursor
uid – user id, assumed to be openerp.SUPERUSER_ID
Methods for OpenUpgrade 8.0Returns
+- Returns:
a dict with ids as keys and with dates as values
Methods for OpenUpgrade 8.0
-- Parameters
+- Parameters:
cr – database cursor
uid – user id, assumed to be openerp.SUPERUSER_ID
Methods for OpenUpgrade 8.0Returns
+- Returns:
-
@@ -1031,7 +1029,7 @@ Methods for OpenUpgrade 8.0
-- Parameters
+- Parameters:
model_name – The name of the model whose aliases are to be updated. The model_id is also set as the aliases’ alias_parent_model_id.
set_parent_thread_id' – When set, set the ids of the resources as their alias’ alias_parent_thread_id
Methods for OpenUpgrade 8.0
+
+
Methods for OpenUpgrade 9.0¶
The following specific methods for 9.0 are available. These have been
developed to cover specific needs as per data model changes in that
@@ -1066,7 +1064,7 @@
Methods for OpenUpgrade 9.0
-Parameters
+Parameters:
env – Odoo environment
field_spec –
A dictionary with the ORM model name as key, and as
@@ -1092,8 +1090,8 @@
Methods for OpenUpgrade 9.0Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
a:before{
- content: "[";
-}
-
-a.brackets:after,
-span.brackets > a:after {
- content: "]";
-}
-
h1:hover > a.headerlink,
h2:hover > a.headerlink,
@@ -334,11 +324,17 @@ aside.sidebar {
p.sidebar-title {
font-weight: bold;
}
+
+nav.contents,
+aside.topic,
div.admonition, div.topic, blockquote {
clear: left;
}
/* -- topics ---------------------------------------------------------------- */
+
+nav.contents,
+aside.topic,
div.topic {
border: 1px solid #ccc;
padding: 7px;
@@ -377,6 +373,8 @@ div.body p.centered {
div.sidebar > :last-child,
aside.sidebar > :last-child,
+nav.contents > :last-child,
+aside.topic > :last-child,
div.topic > :last-child,
div.admonition > :last-child {
margin-bottom: 0;
@@ -384,6 +382,8 @@ div.admonition > :last-child {
div.sidebar::after,
aside.sidebar::after,
+nav.contents::after,
+aside.topic::after,
div.topic::after,
div.admonition::after,
blockquote::after {
@@ -608,19 +608,27 @@ ol.simple p,
ul.simple p {
margin-bottom: 0;
}
-dl.footnote > dt,
-dl.citation > dt {
+
+aside.footnote > span,
+div.citation > span {
float: left;
- margin-right: 0.5em;
}
-
-dl.footnote > dd,
-dl.citation > dd {
+aside.footnote > span:last-of-type,
+div.citation > span:last-of-type {
+ padding-right: 0.5em;
+}
+aside.footnote > p {
+ margin-left: 2em;
+}
+div.citation > p {
+ margin-left: 4em;
+}
+aside.footnote > p:last-of-type,
+div.citation > p:last-of-type {
margin-bottom: 0em;
}
-
-dl.footnote > dd:after,
-dl.citation > dd:after {
+aside.footnote > p:last-of-type:after,
+div.citation > p:last-of-type:after {
content: "";
clear: both;
}
@@ -636,10 +644,6 @@ dl.field-list > dt {
padding-left: 0.5em;
padding-right: 5px;
}
-dl.field-list > dt:after {
- content: ":";
-}
-
dl.field-list > dd {
padding-left: 0.5em;
diff --git a/docs/_static/doctools.js b/docs/_static/doctools.js
index 527b876ca636..d06a71d75180 100644
--- a/docs/_static/doctools.js
+++ b/docs/_static/doctools.js
@@ -4,7 +4,7 @@
*
* Base JavaScript utilities for all Sphinx HTML documentation.
*
- * :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS.
+ * :copyright: Copyright 2007-2023 by the Sphinx team, see AUTHORS.
* :license: BSD, see LICENSE for details.
*
*/
diff --git a/docs/_static/language_data.js b/docs/_static/language_data.js
index 2e22b06ab13b..250f5665fa64 100644
--- a/docs/_static/language_data.js
+++ b/docs/_static/language_data.js
@@ -5,7 +5,7 @@
* This script contains the language-specific data used by searchtools.js,
* namely the list of stopwords, stemmer, scorer and splitter.
*
- * :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS.
+ * :copyright: Copyright 2007-2023 by the Sphinx team, see AUTHORS.
* :license: BSD, see LICENSE for details.
*
*/
diff --git a/docs/_static/searchtools.js b/docs/_static/searchtools.js
index e89e34d4e772..97d56a74d820 100644
--- a/docs/_static/searchtools.js
+++ b/docs/_static/searchtools.js
@@ -4,7 +4,7 @@
*
* Sphinx JavaScript utilities for the full-text search.
*
- * :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS.
+ * :copyright: Copyright 2007-2023 by the Sphinx team, see AUTHORS.
* :license: BSD, see LICENSE for details.
*
*/
diff --git a/docs/after_migration.html b/docs/after_migration.html
index ec9f940a93b5..d302b1f0dbe1 100644
--- a/docs/after_migration.html
+++ b/docs/after_migration.html
@@ -4,14 +4,12 @@
-
+
+
After migration — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
After migration¶
OpenUpgrade keeps old model tables and old columns (prefixed with
openupgrade_legacy_ word) in PostgreSQL as a conservative strategy because
@@ -51,7 +49,7 @@
After migrationQuick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
How to run your own analysis — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
How to run your own analysis¶
If you do need to run your own analysis, you need to perform the following
steps.
@@ -68,7 +66,7 @@ How to run your own analysisQuick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Database analysis — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Database analysis¶
Database analysis files are hosted in scripts subdirectory of the
openupgrade_scripts module directory in the https://github.com/oca/openupgrade
@@ -42,14 +40,14 @@
Database analysishttps://github.com/oca/server-tools.
-
+
Earlier versions¶
In editions earlier than 14.0, the analysis files were hosted in the forks of
Odoo at https://github.com/oca/openupgrade. The module to create the analysis
was placed in each branch of the openupgrade repository under
odoo/addons/openupgrade_records.
-
-
+
+
Contents¶
The contents of the migration directory per module are:
@@ -79,8 +77,8 @@ ContentsFields analysis format
-
-
+
+
@@ -153,8 +151,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Community involvement — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Community involvement¶
Writing migration scripts for Odoo is a lot of work, that can not be
accomplished by a single party. We need your help.
@@ -57,7 +55,7 @@ Community involvement
Thank you!
-
+
@@ -121,8 +119,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
<no title> — OpenUpgrade 16.0 documentation
-
-
-
@@ -106,8 +104,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Migration script development — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,9 +32,9 @@
-
+
Migration script development¶
-
+
Overview¶
The execution of the migration scripts is triggered by the “Migration Manager”:
The Odoo Migration Manager.
@@ -72,8 +70,8 @@ Overviewhttps://github.com/OCA/OpenUpgrade/pull/2275/files.
-
-
+
+
Learn from existing migration scrips¶
Since version 14, the migration scripts are located in:
openupgrade_scripts/scripts/<module-name>
@@ -87,14 +85,14 @@ Learn from existing migration scrips
+
+
Learn from code review of open PRs¶
https://github.com/OCA/OpenUpgrade/pulls
This will engage you in a discussion with other contributors and help you understand
how developers selected one way or another to implement the migration scripts.
-
-
+
+
The Trial and error process for the development of your scripts¶
Basically, this is the happening during the step when you try to run the upgrade
described in Running the migration:
@@ -113,7 +111,7 @@ The Trial and error process for the development of your scripts--update all to ensure that all
dependent modules have been upgraded.
-
+
Restart the upgrade of the failed module instead of upgrading all systematically¶
As an alternative to the step [C] mentioned above…
In case of error, fix the error (adding or editing migration
@@ -127,9 +125,9 @@
Restart the upgrade of the failed module instead of upgrading all systematic
(see explanations here: https://github.com/OCA/OpenUpgrade/pull/2499).
It is available only for 12 and 13:
https://github.com/OCA/OpenUpgrade/pulls?q=is%3Apr+%5BFIX%5D+reset+exception
-
-
-
+
+
+
Learning resources¶
@@ -143,8 +141,8 @@ Learning resourcesopenupgrade.py
-
-
+
+
@@ -222,8 +220,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Development FAQ — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Development FAQ¶
- How are new dependencies treated by the Odoo migration manager?
New dependencies (like the edi module is a new dependency of the
@@ -55,7 +53,7 @@
Development FAQQuick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Fields analysis format — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Fields analysis format¶
The first section displays models which are removed from the database.
The second section displays models which are added to the database.
@@ -109,7 +107,7 @@ Fields analysis format
The final section of the database layout analysis contains a simple report on
the changes that were detected.
-
+
@@ -184,8 +182,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
-
-
@@ -365,8 +362,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
diff --git a/docs/index.html b/docs/index.html
index fe0df29ab857..03696489e9be 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -4,14 +4,12 @@
-
+
+
Welcome to OpenUpgrade’s documentation! — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Welcome to OpenUpgrade’s documentation!¶
If you just want to migrate your database and don’t care about the technical details, refer to Running the migration
Contents:
@@ -187,15 +185,15 @@ Welcome to OpenUpgrade’s documentation!https://oca.github.io/OpenUpgrade
-
+
Indices and tables¶
-
-
+
+
@@ -258,8 +256,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Introduction — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Introduction¶
Odoo is an open source business application suite and development platform.
This project, OpenUpgrade, aims to provide an Open Source upgrade path for
@@ -51,14 +49,14 @@
Introduction
+
Older versions¶
Before Odoo 14.0, the branches in https://github.com/OCA/openupgrade
contain copies (or forks in Git terminology) of the Odoo main project, but
with extra commits that include the framework, and the analysis and the
migration scripts for each module.
-
-
+
+
Contribute¶
In order to contribute to the OpenUpgrade project, please
@@ -68,9 +66,9 @@ Contribute
+
+
+
Migrating your database¶
@@ -85,7 +83,7 @@ Migrating your databaseAfter migration
-
+
@@ -157,8 +155,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Running the migration — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,14 +32,14 @@
-
+
Running the migration¶
Check out the code manually and upgrade your database by calling odoo-bin,
(or openerp-server) directly. You will want to do this when you are working on
developing migration scripts for uncovered modules.
-
+
1. Get the code from OpenUpgrade and dependencies¶
-
+
OpenUpgrade¶
Make the openupgrade_framework and the openupgrade_scripts modules
available in the addons path in the Odoo instance of the new version.
@@ -53,8 +51,8 @@ OpenUpgradehttps://github.com/OCA/openupgrade
-
-
+
+
openupgradelib¶
When installing the openupgradelib make sure you check out the latest version
@@ -64,9 +62,9 @@
openupgradelib
+
+
+
2. Check coverage of the migration scripts for your installed modules¶
Check if there are migration scripts provided for the set of modules that
are installed in your Odoo database. If there are modules for which no
@@ -74,20 +72,20 @@
2. Check coverage of the migration scripts for your installed modulesModule coverage and refer to the Migration script development
documentation to add the missing migration scripts.
-
-
+
+
3. Make a copy of the database to migrate¶
Decide which database you are going to upgrade. You absolutely must make a
backup of your live database before you start this process!
-
-
+
+
4. Adjust the configuration for Odoo and OpenUpgrade¶
Edit the configuration files and command line parameters to point to the
database you are going to upgrade. The recommended command line parameters are the
--update all --stop-after-init --load=base,web,openupgrade_framework flags.
For versions earlier than 14.0 that are running the OpenUpgrade fork rather
than Odoo itself, you do not pass the load parameter.
-
+
Configuration options¶
When migrating across several versions of Odoo, setting the target version
@@ -100,8 +98,8 @@
Configuration options(when migrating up to 13.0)
-
-
+
+
Obsolete options in the Odoo configuration file¶
Versions of OpenUpgrade earlier than 14.0 allow for the following configuration
options. Add these options to a separate stanza in the server configuration
@@ -118,23 +116,23 @@
Obsolete options in the Odoo configuration file
+
+
+
5. Run the upgrade, fix data and repeat…¶
Run the upgrade and check for errors. You will probably learn a lot about
your data and have to do some manual clean up before and after the upgrade.
Expect to repeat the process several times as you encounter errors, clean up
your data, and try again. If necessary, ask for help or report bugs on
Github.
-
+
Write the missing migration scripts¶
At this stage, if some of your modules don’t have yet migration scripts,
you might need to add them yourself.
Read more about the development of migrations scripts in Migration script development
-
-
-
+
+
+
@@ -211,8 +209,8 @@ Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
The Odoo Migration Manager — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
The Odoo Migration Manager¶
The core mechanism that OpenUpgrade relies on is the migration manager that is
already built into Odoo itself. It is this mechanism that was used by Odoo to
@@ -58,7 +56,7 @@
The Odoo Migration ManagerQuick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by Sphinx 5.3.0
- & Alabaster 0.7.12
+ Powered by Sphinx 6.1.3
+ & Alabaster 0.7.13
|
-
+
+
Module coverage 10.0 -> 11.0 — OpenUpgrade 16.0 documentation
-
-
-
@@ -34,7 +32,7 @@
-
+
Module coverage 10.0 -> 11.0¶
Status :
@@ -49,10 +47,6 @@ Module coverage 10.0 -> 11.0. Modules that are
missing in the new release are marked with 
.
http_routing