Hi All,
This post is a result of my earlier discussion regarding the same from a
different perspective.
PATH_TXN_MERGEINFO file having hash of
'paths having svn:mergeinfo' Vs 'actual mergeinfo' has come to life at
r19949.
Corresponding snip from the log reads thus,
<snip>
Mergeinfo is now stored in a transaction-local file during the transaction,
and SQL is generated at commit time.
</snip>
If above snip is the purpose of this implementation, I have the following
thoughts,
a)Why to have it has a disk-based storage?
I am against it for the following reasons
* As this(svn:mergeinfo) data is not meant for sharing with other
tools like 'svnadmin' and
'svnlook', this filebased storage is a wrong choice.
- I have a in-memory equivalent patch for the same.
* It is a joke to keep creating new hash in memory and dump to file
within the
same program execution context for each path having 'svn:mergeinfo'.
- I have another patch which does the same indexing from
'write_final_rev' without caching at all.
* It is a data redundancy issue.
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 Wed Sep 13 12:33:56 2006