Don:
The argumentation given is not solving the issue and it is not consistent with the current implemententation of modules
If at update time, csv are treated as noupdate=True (like in the current status) it is non consistent with the policy on almost 100% of addons, where the security info was placed on update, not init, and overwrites any customer modification
Additionally, it is not wath the doc says, and most important, it could generate a mess on database security!
Please take into account the profound impact this fault could have in actual installations (not demos)
Don:
The argumentation given is not solving the issue and it is not consistent with the current implemententation of modules
If at update time, csv are treated as noupdate=True (like in the current status) it is non consistent with the policy on almost 100% of addons, where the security info was placed on update, not init, and overwrites any customer modification
Additionally, it is not wath the doc says, and most important, it could generate a mess on database security!
Please take into account the profound impact this fault could have in actual installations (not demos)