0012085: The concurrent modification mechanism shouldn't rely only on updated column

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0012085

Openbravo ERP

A. Platform

public

2010-01-28 10:42

2011-05-25 13:03

Reporter

iperdomo

Assigned To

iciordia

Priority

normal

Severity

major

Reproducibility

always

Status

new

Resolution

open

Platform

OS Version

Community Appliance

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0012085: The concurrent modification mechanism shouldn't rely only on updated column

Description

The current implementation of the concurrent modification check, is based only in the updated column.

There are tabs that are based on tables updated by background processes. If you update a record, the updated column should be updated, but if you schedule a process to run every 1 second, you are always watching in the UI an old copy of the record.

The check should be based on the updated column, but also on checking the values of the columns that can be updated by the user.

Steps To Reproduce

* Update your working copy to revision acdd19231c37
* Schedule a process request for the Accounting server to run every 1 second
* Try to unschedule it

Proposed Solution

* The concurrent modification should be based on the updated timestamp but also check the values of the columns that can updated from the UI

Additional Information