[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DB_INCOMPLETE solved, small new problem appearing though

From: <kfogel_at_collab.net>
Date: 2001-08-30 02:21:33 CEST

"Neal Reizer" <nreizer@collab.net> writes:
> Great news! Congratulations!

Thanks, Neal!

Actually though (everyone), I am a little worried about the possible
effects of this problem:

> > I have noticed that the update driver can get confused during those
> > simultaneous checkouts (i.e., a checkout going on during mass-commit)
> > and error out in get_editor.c:847 ("object of same name already
> > exists"). This will need looking into. Have done some detective work
> > already, and have a hypothesis about the cause -- Greg Stein or Ben,
> > if you take a look at issue #468, I think there's a chance you'll know
> > right away what's going on.

Seems to me that it could result in a lying update, that is, your
checkout or update could finish and report that your working copy, or
some portion of it, is at revision X, and yet some objects claiming to
be at X would really have contents as if for Y (where Y > X).

Need to think about this more. For now, I've reclassifed issue #468
as an M3 bug, but would love to be talked out of that, if we can
establish that there's no danger of dishonest updates. :-) Bugs that
cause us inconvenience are okay in M3, but data corruption is another
matter.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:37 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.