Strange Repository File/Folder Information

[Josep Condal]

I'm having my first experiences with SourceGear Vault so I apologize if I state anything so basic.

I added a few files (about 100) in a new install of Vault Server 3.0.7 on W2003.

I did a few updates to some files and some directory moving by sharing to a new directory and deleting the original (I understand this is how you move things in a repository).

Everything seems alright from the client point of view.

However, when checking things out with the Admin tool, if I click on Properties for that repository in the Reporsitories tab I get the following strange information under Repository Information:

Folders 2 (+19 deleted)
Files 0 (+284 deleted)

The above numbers do not make any sense as I see plenty of folders and files in the repository's tree. Am I interpreting this information correctly.

Regards,

Josep.

[jclausius]

The information presented there is incorrect. Furthermore, it is harmless in regards to any operation of the Vault Server.

There is just a count which is incremented when filess are added and decremented when files are deleted. The system doesn't take into account sharing for the file count equation, so this can get out of sync when deleting shares.

If this is getting on your nerves, I can provide a query which will correct the counts.

In regards to moving objects within the repository, a more efficient way to accomplish this is to highlight the file(s) or folder and then invoke Move... from the File menu.

Welcome to Vault. If you have any other questions, please feel free to post them on the Support or Discussion forums.

[Josep Condal]

Thanks, indeed I discovered the Move item in the File menu later, I just have a slow learning curve. I guess that when I did not see a Move option by right-clicking, I just gave for granted it was not there at all.

Regarding the statistic information, if there is already a bug waiting to be fixed in the pipeline, I don't think I need a custom query at this point, but it is good to know that it is no more than a cosmetic problem (i.e. no data-integrity threats).

Thanks,
Josep.