1 message in com.perforce.perforce-userDatabase integrity
FromSent OnAttachments
Mich...@UTS.Itron.com13 Jul 1998 06:09 
Subject:Database integrity
From:Mich...@UTS.Itron.com (Mich@UTS.Itron.com)
Date:07/13/1998 06:09:50 AM
List:com.perforce.perforce-user

That's one that hasn't worried me. The checkpoint/journal mechanism allows me to have flat, editable, copies of the database I can rebuild from in a moment's notice. All of the files are stored in accessable formats within the depot (RCS, gzip, etc.) I know that even if my Perforce database is totally hosed, (1) I can rebuild it, (2) I can get to my files. Perforce's openness has allowed me to work around its few shortcomings, working directly with the database check points and the depot files. Oh, and, I have never had a problem with database integrity on my system.

-----Original Message----- From: Virginie Lamb [SMTP:virginie at perforce.com] Sent: Tuesday, July 07, 1998 1:14 AM To: 'perforce-user at perforce.com' Subject: Database integrity

Hello all,

One of our prospects is worried about database integrity with Perforce. Do you have any thoughts on this issue that you would like to share with us?

Thanks a lot for your time and best regards,

Virginie Lamb

------------------------------------------------------------------------ europe at perforce.com PERFORCE SOFTWARE EUROPE http://www.perforce.com The Fast Software Configuration Management Tool Tel: +33 130 96 67 27 Fax: +33 139 44 94 74

------------------------------------------------------------------------