Olivier Dony
d93148240b
When a `noupdate` record is processed during an update, the update_dummy method marks the record as "seen" so it won't be deleted at the garbage collection step, and seen as an obsolete external ID. This needs to be done also for the parent records via _inherits, because they have also received an implicit external ID at creation, and must not be garbage collected, even if their `noupdate` flag (db side) is not set because the flag was added later. This rare problem could be reproduced by creating a product in a module, then referencing it in e.g. a sales order, then updating the module after changing the product record to be in a `noupdate` block. At the end of the update the implicit product.template record would be garbage collected, and trigger a cascade deletion of its children - blocked by the SO reference to the product.
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
If you are a developer you may type the following command at your terminal:
wget -O- https://raw.githubusercontent.com/odoo/odoo/8.0/odoo.py | python
Then follow the developer tutorials
For Odoo employees
To add the odoo-dev remote use this command:
$ ./odoo.py setup_git_dev
To fetch odoo merge pull requests refs use this command:
$ ./odoo.py setup_git_review