[SAAS-3] Migration script no more called on a fresh database
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Won't Fix
|
Undecided
|
Christophe Simonis (OpenERP) |
Bug Description
In rev http://
The change has only been applied on saas-x and trunk branches but not backported to 7.0. This change is annoying since we no more have the possibility to use the migration machinery when installing a new module. Before the change, it was easy to distinguish in the migration script, a first installation of the module or a simple upgrade and therefore add code for each cases.
When a module was first installed, migration script was called with version set to None
When a module was upgraded migration script was called with the previous installed version.
Now on a fresh install we no longer have a way to use a pre/post installation hook.... It's really blocker for exemple when your module add a unique index on an already existing column and you want to update existing data in a way that the new constraint wil be successfully applied.
Regards,
lmi
Related branches
- OpenERP Core Team: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifiedopenerp/modules/migration.py (+1/-1)
Changed in openobject-server: | |
status: | New → Invalid |
Changed in openobject-server: | |
assignee: | nobody → Christophe Simonis (OpenERP) (kangol) |
assignee: | Christophe Simonis (OpenERP) (kangol) → nobody |
status: | Invalid → In Progress |
assignee: | nobody → Christophe Simonis (OpenERP) (kangol) |
Changed in openobject-server: | |
status: | Invalid → New |
linked to opw-607346