Edgewall Software
Modify ↓

Opened 14 years ago

Last modified 9 years ago

#9478 new defect

Concurrent ticket modifications is still possible

Reported by: Christian Boos Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version: 0.12
Severity: minor Keywords: concurrent save
Cc: leho@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Before saving a ticket modification, we try to detect if the page was not already modified by another user (r5449). However this check is not done within a single transaction, and therefore it can be ineffective if two changes happen concurrently.

See ticket:9235#comment:10 for an example (or comments:10 actually ;-) ).

Attachments (0)

Change History (3)

comment:1 by Remy Blank, 14 years ago

Are you sure about the milestone? Couldn't we just do a SELECT right before the commit to check if there was a collision, and raise an exception in that case? That could be done for 0.12.1.

Note that this issue was probably already present in 0.11, but a lot less likely, as the timestamps with second resolution would generate primary key collisions in most of the cases where this could happen.

comment:2 by Ryan J Ollos, 9 years ago

Similar issue reported in #11491, so that ticket was closed as a duplicate.

comment:3 by lkraav <leho@…>, 9 years ago

Cc: leho@… added

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.