On Mon, Aug 22, 2011 at 20:13, Markus Schaber <m.schaber_at_3s-software.com> wrote:
> Hi, Ivan,
>
> Von: Ivan Zhakov [mailto:ivan_at_visualsvn.com]
>>>> We experienced similar issue with "database table is locked" message in
>>>> VisualSVN and found that disabling SQLite shared cache fixes the problem.
>>>> In our case problem was appearing when background thread running svn
>>>> status on working copy and foreground thread performs read/write
>>>> operations on the same working copy.
>>> How do I disable SQLite shared cache programmatically via SharpSVN? And what's the impact?
>> We had to patch Subversion source code on build time to remove call
>> to function that enables shared cache in SQLite. SQLite shared cache
>> seems to be peformance optimization when same database accessed using
>> different connections. I believe Subversion uses few connection to
>> database, so it should be big performance degradation after disabling
>> shared cache.
>
> I did try with
>
> D:\svntest\brokenwc>"C:\Program Files\VisualSVN\bin\svn.exe" --version
> svn, version 1.7.0-beta3 (Beta 3)
> compiled Aug 12 2011, 13:22:42
>
> The result is that the upgrade fails with a different error message:
>
> D:\svntest\brokenwc>"C:\Program Files\VisualSVN\bin\svn.exe" upgrade
> Upgraded '.'
> Upgraded 'Device'
> Upgraded 'Device\Plc Logic'
> Upgraded 'Device\Plc Logic\Application'
> Upgraded 'Device\Plc Logic\Application\Library Manager'
> svn: E155010: The node 'D:\svntest\brokenwc\.svn\tmp\wcng\Device\Plc Logic\Application\PLC_PRG\svnobj' was not found.
>
>
It's very interesting. It seems that disabling SQLite shared cache
fixes one problem and discovers another. I'm not WCNG expert, may be
other Subversion developers have more knowledge of possible reason of
"The node .. was not found" error.
Bert do you have any ideas why this could happen?
--
Ivan Zhakov
Received on 2011-08-22 21:30:59 CEST