3.0 bug related to folder/file count after obliterating

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Dave Schulte
Posts: 55
Joined: Thu Dec 02, 2004 1:59 pm

3.0 bug related to folder/file count after obliterating

Post by Dave Schulte » Fri Dec 03, 2004 9:35 am

After upgrading our demo installation to 3.0, I noticed that the window that prompts for a repository selection can display negative folder/file count details for the repository after having obliterated a large number of folders and/or files. See the attached for an example screen shot.
Attachments
bug.doc
(32 KiB) Downloaded 343 times

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Fri Dec 03, 2004 9:48 am

Yes the "counters" can be off when deleting / obliterating shared files / folders. It is totally harmless as these values are not used anywhere else within Vault.

If it is really bothering you, please let me know ( click the email button below this post ), and I can send a SQL Query to reset the numbers.
Jeff Clausius
SourceGear

Dave Schulte
Posts: 55
Joined: Thu Dec 02, 2004 1:59 pm

Post by Dave Schulte » Fri Dec 03, 2004 10:38 am

I just wanted you to be aware of this for the next release. No problem. Thanks.

We are continuing our evaluation of your product, and so far so good. One of my main concerns so far is the fact that Vault appears to save each image of a given file as blob in SQL Server, and the given image is not automatically compressed. This leads me to believe that over time, our database image is going to get quite large. Is this true?
Thanks again.

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Fri Dec 03, 2004 10:45 am

That is incorrect.

Most of the information related to a file and its contents at a particular version is stored in a "delta-ized" compressed format.
Jeff Clausius
SourceGear

Post Reply