Re: Subversion database corruption
Re: Subversion database corruption
- Subject: Re: Subversion database corruption
- From: AgentM <email@hidden>
- Date: Thu, 4 Aug 2005 18:05:27 -0500
If anyone is looking for a decent db-backed code revision system,
take a look at monotone:
http://venge.net/monotone/index.html
There is a binary OS X build available.
Monotone is different from the standard CVS/Subversion/Perforce
lineup because of the decoupled nature of repositories (there need
not be a central server- each repository is useful without a server
or can be one). Monotone's backend is SQLite.
I have been using monotone for four months now with minimal issues
(and certainly no corruption) on a 40 MB repository. A backup
consists of copying the SQLite database file to the backup medium.
For more information, browse the tutorial:
http://venge.net/monotone/docs/Tutorial.html#Tutorial
--just a pleased monotone user
On Aug 4, 2005, at 5:25 PM, Andy Lee wrote:
On Aug 3, 2005, at 1:36 PM, Bill Bumgarner wrote:
I had a similar problem with Berkeley DB eating my subversion
repository. After speaking with the subversion developers about
it, I switched to the FSFS backend on all my repositories and have
not had another problem like it.
At least not a problem you know about. My boss pointed me to this
page: <http://svnbook.red-bean.com/en/1.1/ch05.html#svn-ch-5-
sect-1.3>. It seems to suggest that the reason the FSFS backend
doesn't get wedged by corrupted data is because it doesn't *detect*
it. Sounds to me like the version-control equivalent of compiling
with warnings turned off.
Or is that a mischaracterization?
|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-
AgentM
email@hidden
|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-|-
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden