On 23/06/10 11:26, "Borja López Soilán (Pexego)" wrote: > > Today Olivier commented that, as part of the solution of the bug 581137 > <https://bugs.launchpad.net/openobject-server/+bug/581137>, it is > planned to "/write a migration script in 5.0.12 that will force a > recompute of all parent_store objects, to fix existing tables/". > > I think that this kind of problem, the need to perform some migration > operations when upgrading to a new version, is generic enough for us to > add some support for it on the framework.
I didn't have time to reply before your post on the ML, but we do already have such a mechanism. Copy of my reply on #581137: Borja, I'm not sure if this is what you are referring to, but we already have such a mechanism for that (probably not well documented, though), which allows triggering update code when a module is updated. This exists in 5.0 already. We do plan to use it for the migration step I was referring to. This will give you an example of how to use it. Another basic example here: http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/files/head:/hr_holidays/migrations/ _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
