Skip to Content
Menu
This question has been flagged
4 Replies
1950 Views

Hello,


i did this the last time long ago and didn't find a definitive answer.


So could somebody please confirm: Is the database upgrade after the installation of a new Odoo release just necessary for major releases ?


We installed Odoo 13 in september and just run over the last build to fix the problem with AST and Python 3.8.5.


Is there anything to do ? Stopped the service before, installed from deb package as before and restarted service and everything looks ok.


Thanks in advance

Michael

Avatar
Discard
Author

Ok, thanks for the heads up. I was just irritated by the words database upgrade. As i wrote it is v13 from September to the actual november build, so no major upgrade needed.

I am firm, that Odoo stores the xml of views in the database and only applies column changes in models after module reloading, just wasn't sure if there's something else to do.

so running "odoo-bin -d MYDB -c PATH_TO_ODOO_CONF -u all" should be sufficient.

Is --stop-after-init still there in v13 ?

Yes, " -u all " is sufficient. --stop-after-init can still be found in the Odoo v13 source but I have never used the option.

Author

Ok thank you. I successfully did the upgrade. I like to use the --stop-after-init from older Odoo versions as the output stops after generation so i am able to browse through the generation and look for possible errors occured. But propably that's just personal choice

Best Answer

Each time you upgrade the source code, even when it is a minor upgrade like "Odoo 13 September" to "Odoo 13 October", you need to upgrade the database.

XML files are sometimes upgraded and the only way to refresh the XML files inside the database with the XML files from the updated source is via the command line upgrade option (or by upgrading the base module from within the UX).

There is no command-line option available for major releases - that is a service provided via https://upgrade.odoo.com

Avatar
Discard