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

My understanding of state of things on sqlite storage

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Thu, 24 Jan 2008 19:46:13 +0530

Hi All,

I could observe that we no more record mergeinfo in sqlite. This causes
all 5 issue-2897 specific testcases to fail.

But we have a code that does some insertions to sqlite table but not
exercised thanks to r28134.

As we are not recording anything in sqlite, I expected 'log -g and blame
-g' to fail.

Yes they fail, but they are expected to fail since r28948 and hence our
testsuite passes.

With this I tend to think we need to do 3 things,

1)In trunk Make 'get_mergeinfo_for_tree' API to be sqlite independent.

2)In issue-2897 branch make 'get_commit_and_merge_ranges' extract data
from fs rather than from sqlite.
   FYI: issue-2897 only needs equivalent of 'mergeinfo_changed', it does
not use 'mergeinfo'.

3)Remove all traces of sqlite relating to mergeinfo storage.

Let me know in case I misunderstand anything.

With regards
Kamesh Jayachandran

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-24 15:16:34 CET

This is an archived mail posted to the Subversion Dev mailing list.