@MLConsulting, Indeed, undeploying modules is very experimental and should never be done in production installations with OpenERP. This is because modules can do almost what they want at installation, undoing it all properly is just almost impossible: most of what modules do is declarative so it could be undone automatically eventually. Yes, most of, but not all, that's the point.
The best way I know is: backup the database before installing, test and eventually load back the database backup if you need to revert. An other similar way is with people using virtual machines, they revert them if they need. This is also one reason why it's advisable to use 2 distinct environments: test and production, because once in production you can't afford experimenting with modules as you might screw it all or need to rollback. Hope this helps. ------------------------ Raphaël Valyi CEO and OpenERP consultant at http://www.akretion.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=52798#52798 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
