Community mailing list archives
AW: Data/Module update - Graphical Diff and Approve to handle database/module content like views, etc.by
Absolutely true related to best practices…
If I always create custom inherited views they will not be touched but then I need to take care for a lot of inherited views and sequences and all views which are maintained by modules (noupdate=”0”) should therefore be locked automatically that it will not happen that it is changed manually and overwritten on update again. And again, if the parent view has changed in a way that the inherited view will fail…it would be good to review first.
I still like the idea of versioning for all customized inherited views or views itself and even for other data objects to have documentation/awareness on change level in the database itself.
The modules are easily documented in a repositories (at least it should be like that), but database changes are lost easily (if you ignore the daily backup which at least gives you a fallback to a certain time).
Von: Lorenzo Battistini [mailto:firstname.lastname@example.org]
Gesendet: Montag, 21. Juli 2014 11:06
Betreff: Re: Data/Module update - Graphical Diff and Approve to handle database/module content like views, etc.
On 07/20/2014 10:34 AM, Wolfgang Taferner wrote:
> Dear Community, dear Odoo Team,
> I wonder if someone has stumbled across the problem when doing an
> update of a database for minor changes with external_ids
> (noupdate=”0”) that modified content (views, etc.) within the database
> was overwritten without prompting or recognizing the change actively?
> Of course this should be a more technical feature as sometimes changes
> interdepend on each other, but it would be a huge improvement of
> usability for administrators who really know what they do and can then
> decide about changes of data individually during a semi-manual process.
> So they can do updates on database content (very important if you had
> a SaaS database in the first place or sometimes do quick changes for a
> customer in debug mode which are not documented instantly and later
> need to do minor updates on base, etc.) without losing customization
> directly in the database which is not my normal use case but might
> happen for quick changes on demand.
If you want to change the views using the odoo admin interface, you
should always create inherited views (also possible using the 'manage
views' option in debug mode).
Custom inherited views are not touched by the database's updates.
Tel (CH): +41 91 210 23 40
Tel (IT): +39 011 198 25481
TaPo-IT OG, Wolfgang Taferner