-
After migration
+
After migration
OpenUpgrade keeps old model tables and old columns (prefixed with
openupgrade_legacy_ word) in PostgreSQL as a conservative strategy because
they can be used in a later migration script (or to fix an incorrect migration)
@@ -102,7 +103,7 @@
Quick search
-
+
@@ -119,7 +120,7 @@
-
How to run your own analysis
+
How to run your own analysis
If you do need to run your own analysis, you need to perform the following
steps.
@@ -124,7 +125,7 @@ Quick search
-
+
@@ -141,7 +142,7 @@
-
Database analysis
+
Database analysis
Database analysis files are hosted in scripts subdirectory of the
openupgrade_scripts module directory in the https://github.com/oca/openupgrade
repository.
@@ -41,14 +42,14 @@
Database analysis.
-
Earlier versions
+
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
+
Contents
The contents of the migration directory per module are:
-
+
@@ -151,7 +152,7 @@
Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by
Sphinx 4.5.0
+ Powered by
Sphinx 5.0.1
&
Alabaster 0.7.12
diff --git a/docs/community.html b/docs/community.html
index 133658776f88..c2ce88474369 100644
--- a/docs/community.html
+++ b/docs/community.html
@@ -1,7 +1,7 @@
-
+
-
Migration script development
+
Migration script development
-
Learn from existing migration scrips
+
Learn from existing migration scrips
Since version 14, the migration scripts are located in:
openupgrade_scripts/scripts/<module-name>
During the review for a given module, you can follow this process:
@@ -87,13 +88,13 @@
Learn from existing migration scrips
-
The Trial and error process for the development of your 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 :
-
Learning resources
+
Learning resources
-
+
@@ -220,7 +221,7 @@
Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by
Sphinx 4.5.0
+ Powered by
Sphinx 5.0.1
&
Alabaster 0.7.12
diff --git a/docs/devfaq.html b/docs/devfaq.html
index effe704ead3b..cbc9350642c6 100644
--- a/docs/devfaq.html
+++ b/docs/devfaq.html
@@ -1,7 +1,7 @@
-
+
-
+
@@ -182,7 +183,7 @@
-
Welcome to OpenUpgrade’s documentation!
+
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:
@@ -122,7 +123,7 @@
Welcome to OpenUpgrade’s documentation!
-
Indices and tables
+
Indices and tables
-
+
@@ -192,7 +193,7 @@
Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by
Sphinx 4.5.0
+ Powered by
Sphinx 5.0.1
&
Alabaster 0.7.12
diff --git a/docs/intro.html b/docs/intro.html
index 016db3be046f..f13ae4c4c341 100644
--- a/docs/intro.html
+++ b/docs/intro.html
@@ -1,7 +1,7 @@
-
+
-
Introduction
+
Introduction
Odoo is an open source business application suite and development platform.
This project, OpenUpgrade , aims to provide an Open Source upgrade path for
Odoo. This is a community initiative, as the open source version of Odoo
@@ -50,14 +51,14 @@
Introduction
-
Contribute
+
Contribute
In order to contribute to the OpenUpgrade project, please
-
+
@@ -155,7 +156,7 @@
Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by
Sphinx 4.5.0
+ Powered by
Sphinx 5.0.1
&
Alabaster 0.7.12
diff --git a/docs/migration_details.html b/docs/migration_details.html
index 61e731a64864..f3a041bd5a05 100644
--- a/docs/migration_details.html
+++ b/docs/migration_details.html
@@ -1,7 +1,7 @@
-
+
-
Running the migration
+
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
+
1. Get the code from OpenUpgrade and dependencies
-
OpenUpgrade
+
OpenUpgrade
Make the openupgrade_framework and the openupgrade_scripts modules
available in the addons path in the Odoo instance of the new version.
Or, for older versions: check out the OpenUpgrade source code from Github
@@ -53,7 +54,7 @@
OpenUpgrade
-
openupgradelib
+
openupgradelib
-
3. Make a copy of the database to migrate
+
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
+
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
+
Configuration options
When migrating across several versions of Odoo, setting the target version
as an environment variable allows OpenUpgrade to skip methods that are called
@@ -100,7 +101,7 @@
Configuration options
-
Obsolete options in the Odoo configuration file
+
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
file under a header [openupgrade]
@@ -119,14 +120,14 @@
Obsolete options in the Odoo configuration file
-5. Run the upgrade, fix data and repeat…
+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
+
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
@@ -192,7 +193,7 @@
Quick search
-
+
@@ -209,7 +210,7 @@
Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by
Sphinx 4.5.0
+ Powered by
Sphinx 5.0.1
&
Alabaster 0.7.12
diff --git a/docs/migrationmanager.html b/docs/migrationmanager.html
index 525cf491d000..d358f99ab79b 100644
--- a/docs/migrationmanager.html
+++ b/docs/migrationmanager.html
@@ -1,7 +1,7 @@
-
+
@@ -11,6 +11,7 @@
+
@@ -33,7 +34,7 @@
-
The Odoo Migration Manager
+
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
run migrations back in the days before TinyERP 4.2 when migration scripts where
@@ -116,7 +117,7 @@
Quick search
-
+
@@ -133,7 +134,7 @@
Quick search
©2012-2021, Odoo Community Association (OCA) / The OpenUpgrade developers.
|
- Powered by
Sphinx 4.5.0
+ Powered by
Sphinx 5.0.1
&
Alabaster 0.7.12
diff --git a/docs/modules100-110.html b/docs/modules100-110.html
index 4061b8fe798f..73dacaaec5d5 100644
--- a/docs/modules100-110.html
+++ b/docs/modules100-110.html
@@ -1,7 +1,7 @@
-
+
@@ -11,6 +11,7 @@
+
@@ -33,7 +34,7 @@
-
Module coverage 10.0 -> 11.0
+
Module coverage 10.0 -> 11.0
Status :