It's not dead, it's just resting... This and related issues have been rumbling on for years: https://bugs.launchpad.net/openobject-server/+bug/397741 https://bugs.launchpad.net/openobject-server/+bug/1023615 https://bugs.launchpad.net/openobject-server/+bug/1024114
For xml files a hitherto secret 'solution' is to add forcecreate="False" to every record you don't want updated. Without this deleted records will be recreated even with noupdate="True". For csv files I just comment out all the files I don't want updating in __openerp__.py after the first install. This is obviously not satisfactory for modules that other people might use. The official position seems to be that you should make a separate module containing all your post-installation modifications using the module-recorder so you can reapply them after an update. This requires that you: 1) remember to make a new module before every update 2) remember which objects you have modified, or know which ones will be overwritten 3) are smart enough to figure this out for yourself before the first time you update or you're screwed. On the upside it means that __openerp__.py can be simplified. Big win! -- You received this bug notification because you are a member of OpenERP Indian Team, which is subscribed to OpenERP Server. https://bugs.launchpad.net/bugs/510668 Title: init_xml also updates security/ir.model.access.csv Status in OpenERP Server: Invalid Bug description: if we provide a security/ir.model.access.csv file for access rights on init_xml instead update_xml, it also updates the csv though it was shifted to init_xml..... To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-server/+bug/510668/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openerp-india Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-india More help : https://help.launchpad.net/ListHelp
