Locking bugs temporarily?
Max Kanat-Alexander
mkanat at bugzilla.org
Tue Feb 28 08:07:11 UTC 2012
On 02/27/2012 01:41 AM, Gervase Markham wrote:
> However, this doesn't solve the problem - my extension does not have the
> ability to talk to a "user" to resolve any mid-airs. Therefore, the
> mid-air needs to appear on the screen of the _other_ guy trying to
> change the bug - the real person. That means, I need to have a "lock" or
> something on the bug while I'm changing it, so that when the lock is
> released, _their_ change fails. I don't want users normally using the
> web interface to get a lock, only to respect my lock! :-))
Okay. I'm not sure why the user isn't getting a mid-air. Are you not
updating delta_ts? It's theoretically possible for Bugzilla to have
conflicting transactions that both go through and both happen after the
mid-air check, but the probability is extremely small. Other than that,
as long as you're updating delta_ts, there's no way for two changes to
happen without mid-airs unless both of them are API clients who aren't
respecting the mid-air protection.
-Max
--
Max Kanat-Alexander
Chief Architect, Community Lead, and Release Manager
Bugzilla Project
http://www.bugzilla.org/
More information about the developers
mailing list