[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: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2006-08-31 07:57:01 CEST

>> >> 2. Currently we track 'mergedfrom', 'mergedto' paths in the sqlite
>> db.
>> >> This is not correct, rather we should maintain 'nodeid' and
>> 'copyid'
>> >
>> > Actually, this is wrong. You can use the paths just fine.
>> What if I delete /my_merged_to_path and recreate?
>> The earlier merge history no more applicable for /my_merged_to_path.
> Yes, so?
> when you delete it, you will get a property delete, and we will mark
> the megreinfo as having changed in that revision, with a now empty
> mergeinfo.

I remember you were saying eventually we will move out of
'svn:mergeinfo' prop for merge history tracking.
Moreover get_mergeinfo hook(which will soon be used by the wc-wc merges)
relies on sqlite db for 'merge history retrieval'.

With regards
Kamesh Jayachandran

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 31 07:57:22 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.