Recording the BDB version in the repository

In another thread there has been discussion of issues with accessing
repositories with a version of subversion linked with different versions of
DBD. Specifically, when accessing it with a newer version of subversion
linked against an older BDB. The issue being that you just get really odd
untraceable error messages from the BDB libraries making it hard to
diagnose.

I was wondering if it might makes sense for the DBD backend to record the
version of BDB used to create the database, perhaps in a file in the
repo/db directory, which could then be used to validate the BDB version we
are using to access it.

There would be a lot to consider, such as whether writing to it with a
newer version should update the version etc. But perhaps at a minimum a
warning the version has changed might be in order?

Perhaps someone with more insight into the DBD implementation could have a
think about what if any validation this might allow us to do?

-apw

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 16 17:36:43 2004