subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <b...@qqmail.nl>
Subject RE: Recursion / reentrancy in SVN 1.7
Date Thu, 15 Sep 2011 10:48:44 GMT


> -----Original Message-----
> From: Stefan Sperling [mailto:stsp@elego.de]
> Sent: donderdag 15 september 2011 11:28
> To: Markus Schaber
> Cc: users@subversion.apache.org
> Subject: Re: Recursion / reentrancy in SVN 1.7
> 
> On Thu, Sep 15, 2011 at 10:41:58AM +0200, Markus Schaber wrote:
> > Hi,
> >
> > In our SharpSVN-based software, we happened to have recursive calls to
> > GetStatus inside the progress notification handlers. This worked fine
> > using SVN 1.6, but now with SVN 1.7, some operations like Checkout throw
> > an Exception, due to the working copy database being locked.
> >
> > Maybe our internal design is suboptimal in this case, and I've
> > successfully developed a workaround, so it is not critical.
> >
> > But this still is a regression.
> 
> This is an sqlite limitation. We cannot do much about it without
> taking a huge performance hit.

No, it doesn't have to be a sqlite limitation, it could be a difference
between the old loggy code and how we handle the working queue now. 
If there are workingqueue operations we don't allow opening the database at
all, while we used to allow reading the entries for things like status.

What kind of error do you get?
(The SharpSvn stacktrace isn't really interesting for the users on this
list, but the message that is part from the trace matches exactly what you
would get from svn)

	Bert


Mime
View raw message