@pokoli: Thank you so much for extending instructions on the update process. Such really is crucial - at least if you want non-programmers and geeks as tryton users.
Here is a suggestion for some further extension - I think it’s necessary; at least I never came in touch with the trytond-console within 2 years of trytoning and DO need explanation at this point.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
There are several types of actions to be done:
[SQL]
You should execute the mentioned query on your database. We normally include the BEFORE or AFTER keyword to indicate if the sql should be execute before or after the update processs.
In docker, you need to use a command like
xxx xxx xxx
With a pip setup, go like:
psql -d [name-of-new-database-new-version] -U [name-of-database-owner]
This opens a psql prompt for the listed [SQL] commands
[CONSOLE]
In docker, go:
docker run --rm -ti tryton/tryton trytond-console -d [name-new-database-new-version]
In a pip setup:
$ cd [path-to-tryton_installation]
$ bin/trytond-console -d [name-new-database-new-version]
This opens a trytond-console for the listed [CONSOLE] commands
[PY]
You should update the Python code of your custom modules.
xxx more details
[XML]
You should update the XML code of your custom modules
xxx more details
Also note that some actions depend on the activated modules and can be skipped if the modules are not activated on your database.