On Thu, Apr 18, 2013 at 10:05 PM, Bert Huijben <bert_at_qqmail.nl> wrote:
> Johan Corveleyn reported that he heard multiple reports of this being caused
> by earlier SvnKit versions. I have not got a single bugreport of this type
> for AnkhSvn via our error reporting infrastructure.
> I don’t see how anybody using SQLite can cause this as the updating of the
> reference count is only handled by the triggers...
> But SvnKit implemented their own clone, which used to have problems in this
Indeed. But those errors have since been fixed (have not seen such
problems anymore in the last half year or so).
On Thu, Apr 18, 2013 at 9:55 PM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> I think we should do something to improve the situation. Fortunately it
> seems to be relatively rare, as not many people have complained about it,
> but there are over 5000 pages listed by Google with that error message.
Big +1 from me.
See my own prodding for improvement in this area.
FWIW, I don't buy the argument that svn / sqlite can't break. Bugs (or
rare cosmic ray disturbances or whatever) do happen. Having an 'svn
repair' / 'svn validate' command or something (like SmartSVN's
'validate admin area') would definitely be nice.
Received on 2013-04-18 23:05:49 CEST