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

Re: [PATCH][merge-tracking]sqlite mergeinfo indexing for bdb repositories

From: Daniel Rall <dlr_at_collab.net>
Date: 2006-10-12 00:21:11 CEST

On Wed, 11 Oct 2006, Daniel Rall wrote:
> I chatted with Mike Pilato about this a bit. If we're initially using
> sqlite for the merge info index, we should not be attempting to
> store/retrieve merge info properties as structured data! They should
> be stored simply as atoms.
> If we wanted to jump directly to storing merge info in BerkeleyDB,
> we'd need to replace all usage of the sqlite-based svn_fs_merge_info.h
> APIs in the BDB backend. While we continue prototyping an end-to-end
> Merge Tracking solution, I would prefer to avoid this redundancy for
> the sake of simplicity.
> I've tweaked the patch accordingly, and updated the doc string for
> svn_fs_base__dag_commit_txn() (which was not updated in the previous
> patches).

I'm attaching the latest version of the patch, without removal of the
fs_skels.c changes. Removing the fs_skels.c change requires
additional modifications to revs-txns.c.

> I'm also seeing 'stat_tests.py 20' fail over ra_local under BDB on the
> merge-tracking branch. I have not confirmed whether that failure is
> related to these changes. (I seem to recall you mentioning this in
> one of our previous conversations, but don't recall exactly what'cha
> said.)

I've confirmed that 'stat_tests.py --fs-type=bdb 20' fails both with
and without this patch.

  • application/pgp-signature attachment: stored
Received on Thu Oct 12 00:23:24 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.