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

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

defect

0011879

2.50MP12

closed

iperdomo

Autosave+Process request window

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2010-01-28 10:42	iperdomo	New Issue
2010-01-28 10:42	iperdomo	Assigned To	=> alostale
2010-01-28 10:43	iperdomo	Summary	The concurrent modification mechanism shouldn't rely only un updated column => The concurrent modification mechanism shouldn't rely only on updated column
2010-01-28 10:44	iperdomo	Relationship added	related to 0011879
2010-02-01 12:02	alostale	Assigned To	alostale => iciordia
2010-02-01 12:02	alostale	Type	defect => feature request
2011-05-25 13:03	dmitry_mezentsev	Target Version	3.0MP0 =>