Locking bugs temporarily?

[Max Kanat-Alexander]

	My original plan for the API on this was to allow people to pass a
parameter to Bug.update, perhaps "check_conflicts => (time)", which
would then return an error if there had been changes since the specified
time. The error would include the changes that had been made, in enough
detail that an external app could re-create the "mid-air collision" page
that Bugzilla currently has in its UI.

	One of the pre-requisites to this would be moving the mid-air collision
logic into something re-usable in Bugzilla::Bug or something.

	-Max

On 02/24/2012 06:30 AM, Gervase Markham wrote:
> I have an extension which integrates Bugzilla with another system. At
> the moment, it's possible for me to get a Bug object and, while I am
> working out how to change it as part of the sync, for someone else to
> update the bug. My changes then overwrite theirs. Obviously, there's a
> fairly small time window, but occurrences of this have been noted.
> 
> I can't really implement conflict resolution logic - that needs a human.
> So I'd really like to lock the bug when I get a copy, make my update
> e.g. 2 seconds later, unlock it, for their change to then try and be
> committed and for _them_ (the human) to get a mid-air that they can
> resolve however they like.
> 
> Is it possible to temporarily lock a bug? Either within Bugzilla or
> using a direct database command on a table row? Would that screw things
> up? Is there a better way of solving this?
> 
> We are using MySQL and, at the moment, Bugzilla 3.6.
> 
> Thanks,
> 
> Gerv
> _______________________________________________
> dev-apps-bugzilla mailing list
> dev-apps-bugzilla at lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=mkanat@bugzilla.org>


-- 
Max Kanat-Alexander
Chief Architect, Community Lead, and Release Manager
Bugzilla Project
http://www.bugzilla.org/