How to deal with safe updates/inserts that do not use to_be_updated
Created by: Henrik tom Wörden
The current mechanism expects that the updates are in cfood.to_be_updated. However, in some cases this is not the case. (Example. assert_has_parent(el, "ParRT") and assert_obj_is_in_list(el2, el, datatype=db.LIST("ParRT"); The first update needs to be done directly as the second otherwise may fail with unqualified reference error.)
However, in that case there is no mechanism that would allow to authorize the change.