| Thread Previous • Date Previous • Date Next • Thread Next |
On 01/02/2013 02:16 AM, Phillip Frost wrote:
[1] http://doc.openerp.com/v6.1/developer/11_upgrade_and_migration.html "The creation (or modification in the case of an upgrade) of SQL tables is automated thanks to the description of objects in the server." "The upgrade from version to version is automatic and doesn’t need any special scripting on the user’s part."
Hi Philip,These statements, from the developer documentation, are true in the following sense: if a newer version of a module contains a change in the database layout, neither the developer of the module nor the user who installs it need to bother with SQL statements. The OpenERP module loading process takes care to adapt the database layout according to the model and fields description in the module.
However, if any existing *data* needs to be adapted, the developer needs to write a migration script to do so. The OpenERP server contains a mechanism to run such migration scripts included in the module.
Now, an upgrade from one major version of OpenERP to another comes with a number of changes that require existing data to be manipulated. It is this manipulation of existing data in the case of a major upgrade that is the paid migration offer of OpenERP SA. This is stated in various places on the OpenERP website and in the documentation. If the statements above aimed at module developers seem to imply a free migration between major versions I am sure it is not intentional.
Most likely, OpenERP SA maintain a set of closed source migration scripts for the official addons to perform the upgrades internally. The aforementioned OpenUpgrade project aims at developing open source counterparts of these scripts.
Best regards, Stefan.
| Thread Previous • Date Previous • Date Next • Thread Next |
