Re: versioning unversioned metadata + anonsvn strategies....

Perry E. Metzger wrote:

>>You need to get over that fear. ;~) Replace the word "subversion" in
>>that paragraph with "Oracle" or "SQLServer" and you'll see exactly how
>>crazy that scheme sounds.
>
>
> I dump all my postgres databases to text files.

For every commit??? Sure, do the backups nightly (or hourly), but dumping the
database for every rev (even with an incremental) is, to put it delicately,
quite insane. ;~)

>
> Also, I was at a company once some years ago where the version control
> system, run inside a database, went corrupt and lost weeks of
> work.

Was that VSS by any chance? ;~o

>
> Also, in the last few days someone wrote about how their (apparently
> buggy version of) db ate their revisions.

Berkeley 4.1 has documented problems and it has been known for some time that it
has problems. Unfortunately, not _everyone_ had problems (I had them myself) so
it was very hard to forbid its use with subversion. In fact, I believe that 4.1
was the only version that worked for OS/X (don't quote me). However, now that
4.2 has been released, there is no reason not to prohibit 4.1 (in the
'configure' code), and require either 4.0.x or 4.2 in order to build the files.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org