Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000424Openbravo ERPA. Platformpublic2008-05-26 09:272011-06-12 21:07
Reporteralostale 
Assigned Toiciordia 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version3.0MP0 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0000424: User transaction integrity management
DescriptionWAD generated code does not notice a dirty write where two or more users
are making conflicting changes.

Scenario:

User A is starting to edit the sales order.
User B is starting to edit the sales order.

User A saves the sales order.
User B saves the sales order.

Changes made by the user A are lost

Things to do:

1. At least prevent the write to the dirty data (User B saves).

2. Try not to lcose changes mady by the user B -> browser back and display
some indication that the user should manually open new window and do the
merge or start all ower again.

3. Provide merge aid, by getting the updated data from the DB and side by
side data that user inputed. By clicking the imputed data it will be
overwrite the version coming from the database.
Steps To Reproduce
Proposed Solution
Additional Information
TagsReleaseCandidate
Relationships
has duplicate feature request 0006345 closed pjuvara Two concurrent users on one menu 
blocks feature request 00005012.50 closed pjuvara Data access layer 
Attached Filespng LockingMechanismMessage.png (57,436) 2011-06-12 21:04
https://issues.openbravo.com/file_download.php?file_id=4197&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2008-05-26 09:27alostaleNew Issue
2008-05-26 09:27alostaleAssigned To => cromero
2008-05-30 19:24pjuvaraTag Attached: ReleaseCandidate
2008-05-30 19:24pjuvaraAssigned Tocromero => pjuvara
2008-05-30 19:24pjuvaraStatusnew => acknowledged
2008-05-30 19:25pjuvaraSummaryAvoid dirty write for WAD windows => Conflict management
2008-05-30 19:26pjuvaraSummaryConflict management => User transaction integrity management
2008-05-30 19:31pjuvaraTag Detached: ReleaseCandidate
2008-05-30 19:31pjuvaraRelationship addedblocks 0000501
2008-10-28 10:46pjuvaraTag Attached: ReleaseCandidate
2008-12-07 19:52pjuvaraRelationship addedhas duplicate 0006345
2009-05-22 19:34pjuvaraAssigned Topjuvara => iciordia
2011-04-25 15:55pjuvaraStatusacknowledged => scheduled
2011-04-25 15:55pjuvarafix_in_branch => pi
2011-04-25 15:55pjuvaraNote Added: 0036070
2011-04-25 15:55pjuvaraStatusscheduled => resolved
2011-04-25 15:55pjuvaraFixed in Version => 3.0
2011-04-25 15:55pjuvaraFixed in SCM revision => NA
2011-04-25 15:55pjuvaraResolutionopen => fixed
2011-06-12 21:04iciordiaFile Added: LockingMechanismMessage.png
2011-06-12 21:07iciordiaNote Added: 0038274
2011-06-12 21:07iciordiaStatusresolved => closed

Notes
(0036070)
pjuvara   
2011-04-25 15:55   
Solved in 3.0 with all generated windows going through DAL
(0038274)
iciordia   
2011-06-12 21:07   
Tested in both Form and Grid, the system does not allow dirty editions and returns a proper message (see attached image captured during the testing). Request 2 and 3 are not solved but can not be considered a defect (maybe can be converted into a FR).

Ismael