Closed (fixed)
Project:
Version Control API
Version:
6.x-2.x-dev
Component:
API module
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
8 Feb 2011 at 21:56 UTC
Updated:
15 Apr 2014 at 22:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sdboyer commentedI don't see any necessary connection to #1009164: Add transaction support for big inserts. That's fundamentally about performance, this is a more generalized logic flaw.
The initial thought I had is to switch to using a timestamp in the 'locked' field, indicating when the lock was generated. That'll help us make intelligent decisions about when to clear it.
Comment #2
marvil07 commentedComment #3
marvil07 commentedHere the first step: use timestamp on repository locked database field.
Git backend naturally would need a patch, that I am attaching here for now.
Comment #4
sdboyer commentedfollowup patch
Comment #5
sdboyer commentedComment #6
marvil07 commentedMinor doc change on the vc api patch, and committed.
I also committed the change for vc git.