diff options
| author | Olivier Dony <odo@openerp.com> | 2015-03-18 12:44:44 +0100 |
|---|---|---|
| committer | Olivier Dony <odo@openerp.com> | 2015-03-18 14:10:18 +0100 |
| commit | d93148240b9149fd222eed30e04a0e151a1697c4 (patch) | |
| tree | bbe41d51afb45ccde8d4daf33b548c5fe6ff166b /addons/analytic_user_function | |
| parent | d8c4e4fa76c2eb6e70b6f2711de2e580af81740c (diff) | |
[FIX] ir.model.data: update_dummy should mark `inherits` parents too
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.
Diffstat (limited to 'addons/analytic_user_function')
0 files changed, 0 insertions, 0 deletions
