baef4d3d92
The delete-rule was initially set to `cascade` in revision 6897.16.13 revid:odo@openerp.com-20120705141706-5gm5mmqode3bvkuc because the ORM would not allow anything else for the FK of an _inherits relationship. This constraint was later lifted in 7.0 server at revision 4681 revid:odo@openerp.com-20121212210247-emrz5rf9ewcwdggu so we can now switch to the intended default behavior: when deleting mail aliases we never want to cascade delete the child records, as that could lead to unwanted deletions. On the other hand the aliases are automatically deleted when the record they belong to is deleted, as a kind of internal dependency. This is the intended safe way to delete them. There is a special case when the same alias is manually set on multiple records, in which case you will not be able to delete any of those records. This is an acceptable exception and should be manually handled if ever needed, by temporarily linking the records to delete to new dummy aliases. bzr revid: odo@openerp.com-20130827150708-62hqk8p7twd527n0 |
||
---|---|---|
.. | ||
i18n | ||
report | ||
security | ||
static/src/img | ||
test | ||
wizard | ||
__init__.py | ||
__openerp__.py | ||
board_hr_recruitment_statistical_view.xml | ||
hr_recruitment.py | ||
hr_recruitment_data.xml | ||
hr_recruitment_demo.yml | ||
hr_recruitment_installer_view.xml | ||
hr_recruitment_menu.xml | ||
hr_recruitment_view.xml | ||
res_config.py | ||
res_config_view.xml |