Comment 2 for bug 1024114

Looking for bugs related to CSV files and noupdate, I found two. Bug 397741 complained about security settings from the CSV files overwriting what the users had changed in the database. It asked for CSV files to be treated as noupdate="1", but was closed as invalid. Bug 787256 complained that failed CSV imports did not get rolled back, and it's been in the triaged state since June 2011. That bug is not particularly related to the noupdate attribute, but it did include the following in comment #4 from Olivier Dony.

>Note that there is a legacy difference between CSV files that are in the 'update_xml' section of
>the __openerp__ vs those in the init_xml/data sections. The former are in noupdate=False
>mode, the latter are in noupdate=True mode.