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

Re: [merge-tracking] points of improvement in mergetracking sqlite db design

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-09-12 14:22:21 CEST

On 9/12/06, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
> On Mon, Sep 11, 2006 at 01:00:17PM -0700, Daniel Rall wrote:
> > > >I remember you were saying eventually we will move out of
> > > >'svn:mergeinfo' prop for merge history tracking.
> > >
> > > I said some people would like to do that. I have no personal plans to
> > > implement it :)
> >
> > For the record, "some people" includes me. I've had too many bad
> > experiences with needing to keep redundant data in sync between
> > multiple data stores to want to add such a thing into a new system.
> (I agree). Could you clarify whether you're planning to keep the
> mergeinfo information _visible_ via properties, even if it's not stored
> as such in the backend?
> i.e. will the only difference between the existing system and what
> you're proposing be where the data is stored, or are you planning on
> taking the whole mergeinfo information completely out-of-band as well?

From the conversations I've had with Dan about it, I believe it's only
the back end storage that will change, it will still show up as
properties to the client.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 12 14:22:58 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.