Community mailing list archives
Re: Data/Module update - Graphical Diff and Approve to handle database/module content like views, etc.
AW: Data/Module update - Graphical Diff and Approve to handle database/module content like views, etc.by
Well, it is not about the mechanism of noupdate itself which is pretty clear and straight forward.
It is about versioning of data b/c sometimes it makes sense to update for example views by the publisher/maintainer which might be also used and changed by the user/administrator since the last update.
These records/attributes which actually hold data structures in a text field must be tracked at some point and introduce a mechanism to handle those two-ways.
I would love to have versions on these fields and a graphical diff/merge way to “own” the data - even if you only have access to the database (SaaS) - all the way and not lose them OR deny updates from maintainer/publisher (in the update/upgrade process).
I hope you can see where the idea/problem comes from and it perfectly makes sense if you think about the newly introduced CMS pages and handling these along with improvements from Odoo Core or just simply stepping back in your own work b/c something went wrong with a saved record at some point.
Von: Lionel Sausin [mailto:email@example.com]
Gesendet: Montag, 21. Juli 2014 09:40
Betreff: Re: Data/Module update - Graphical Diff and Approve to handle database/module content like views, etc.
Le 20/07/2014 10:34, Wolfgang Taferner a écrit :
> 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?
Maybe if you think some more records deserve to be user-updatable, you
should file bug reports to have them set noupdate=1?
TaPo-IT OG, Wolfgang Taferner