David Glasser wrote:
> From reading index_path_mergeinfo (the only function with any
> INSERTs), it sure looks like mergeinfo_changed contains no information
> not already in mergeinfo. It looks like (rev, path) is in
> mergeinfo_changed if and only if there exists (from, start, end,
> inheritable) such that (rev, from, path, start, end, inheritable) is
> in mergeinfo. Am I missing something?
>
>
I originally thought it served as a kind of peg revision. Now I see no
use in this table. Probably it exist to check the elided mergeinfo
faster with *relativey less number of records* than doing a query on
'mergeinfo table' which will have huge number of records due to full
text mergeinfo.
But in my issue-2897 branch it serves a purpose of tracking what exactly
merged in a commit, which 'mergeinfo'(fulltext mergeinfo) table cannot do.
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 Tue Nov 27 07:09:11 2007