Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0000424
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. PlatformminorN/A2008-05-26 09:272011-06-12 21:07
ReporteralostaleView Statuspublic 
Assigned Toiciordia 
PrioritynormalResolutionfixedFixed in Version3.0MP0
StatusclosedFix in branchpiFixed in SCM revisionNA
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0000424: 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.
TagsReleaseCandidate
Attached Filespng file icon LockingMechanismMessage.png [^] (57,436 bytes) 2011-06-12 21:04

- Relationships [ Relation Graph ] [ Dependency Graph ]
has duplicate feature request 0006345 closedpjuvara Two concurrent users on one menu 
blocks feature request 00005012.50 closedpjuvara Data access layer 

-  Notes
(0036070)
pjuvara (reporter)
2011-04-25 15:55

 Solved in 3.0 with all generated windows going through DAL
(0038274)
iciordia (manager)
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

- Issue History
Date Modified Username Field Change
2008-05-26 09:27 alostale New Issue
2008-05-26 09:27 alostale Assigned To => cromero
2008-05-30 19:24 pjuvara Tag Attached: ReleaseCandidate
2008-05-30 19:24 pjuvara Assigned To cromero => pjuvara
2008-05-30 19:24 pjuvara Status new => acknowledged
2008-05-30 19:25 pjuvara Summary Avoid dirty write for WAD windows => Conflict management
2008-05-30 19:26 pjuvara Summary Conflict management => User transaction integrity management
2008-05-30 19:31 pjuvara Tag Detached: ReleaseCandidate
2008-05-30 19:31 pjuvara Relationship added blocks 0000501
2008-10-28 10:46 pjuvara Tag Attached: ReleaseCandidate
2008-12-07 19:52 pjuvara Relationship added has duplicate 0006345
2009-05-22 19:34 pjuvara Assigned To pjuvara => iciordia
2011-04-25 15:55 pjuvara Status acknowledged => scheduled
2011-04-25 15:55 pjuvara fix_in_branch => pi
2011-04-25 15:55 pjuvara Note Added: 0036070
2011-04-25 15:55 pjuvara Status scheduled => resolved
2011-04-25 15:55 pjuvara Fixed in Version => 3.0
2011-04-25 15:55 pjuvara Fixed in SCM revision => NA
2011-04-25 15:55 pjuvara Resolution open => fixed
2011-06-12 21:04 iciordia File Added: LockingMechanismMessage.png
2011-06-12 21:07 iciordia Note Added: 0038274
2011-06-12 21:07 iciordia Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker