Re: sqlite locking and svn client concurrency

2012-10-31 Thread Philip Martin
Johan Corveleyn writes: > If this is hard to handle in practice, and a long running > multi-threaded client has to wait anyway for an entire write operation > to be finished, I'm wondering if it would be much easier for such > clients to also always use the "exclusive locking" mode. It would make

Re: sqlite locking and svn client concurrency

2012-10-31 Thread Johan Corveleyn
On Fri, Oct 26, 2012 at 4:10 PM, Philip Martin wrote: > Johan Corveleyn writes: > >> - This 10 second timeout, for a read operation that is blocked by some >> write transaction: is this implemented somewhere in the svn source >> code (if so, where?), or is this some configuration setting for the

Re: sqlite locking and svn client concurrency

2012-10-26 Thread Philip Martin
Johan Corveleyn writes: > - This 10 second timeout, for a read operation that is blocked by some > write transaction: is this implemented somewhere in the svn source > code (if so, where?), or is this some configuration setting for the > sqlite connection or something like that? It's hard-coded,

sqlite locking and svn client concurrency (was: svn commit: r1398389)

2012-10-24 Thread Johan Corveleyn
I'd like to discuss this topic a bit further, to try and understand things more. On Thu, Oct 18, 2012 at 7:04 PM, Julian Foad wrote: > Philip Martin wrote: >> Johan Corveleyn writes: >> >>> With this new "exclusive" mode it's probably quite clear (no >>> parallellism possible at all), but beca