Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Concurrency write check
by
Efatto.it di Sergio Corato, Sergio Corato
Hi Tom,
I think this check should always be called, because it's a security check.
It should work the way you described.
I looked for some tests with no luck, maybe I didn't check in the right place?
Many thanks
Sergio Corato
Il giorno gio 15 feb 2024 alle ore 12:02 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:
It looks like it only actions when CONCURRENCY_FIELD ("__last_update") is defined in the context, maybe that's why it's not triggering for you? The functionality seems indeed to be that whenever someone tries to save a change on a form view of something that someone else saved meanwhile, it drops out with a validation error. Perhaps they added the context key just to be able to test with this functionality before rolling it out? On 2/14/24 18:27, Sergio Corato wrote: > Hi, > I haven't found a way to check if the concurrency check here works: > https://github.com/odoo/odoo/blob/14.0/odoo/models.py#L3251 > Shouldn't it warn/block if someone tries to write on a field that has > been modified in the meanwhile? > Sergio Corato > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
